chromium: Fix SIGILL on RPI4

Signed-off-by: Khem Raj <raj.khem@gmail.com>

Author: kraj

meta-chromium/recipes-browser/chromium/chromium-gn.inc

@@ -35,6 +35,7 @@ SRC_URI += " \
     file://0037-Fix-constexpr-variable-cannot-have-non-literal-type-.patch \
     file://0038-Fix-undefined-symbol-PaintOpWriter-SerializedSize-un.patch \
 "
+SRC_URI:append:aarch64 = "${@bb.utils.contains('TUNE_FEATURES', 'crypto', '', ' file://boringssl_no_asm_config.patch', d)}"
 
 SRC_URI:append:libc-musl = "\
     file://musl/0001-mallinfo-implementation-is-glibc-specific.patch \

meta-chromium/recipes-browser/chromium/files/boringssl_no_asm_config.patch

@@ -0,0 +1,18 @@
+Disable assembly routines on arm64/rpi4 since it uses
+AES crypto extentions and these extentions do not exist in rpi4
+
+This fixes random SIGILL seen in aes_hw_set_encrypt_key() on rpi4-64
+
+Upstream-Status: Inappropriate [Specific to armv8 minus crypto]
+Signed-off-by: Khem Raj <raj.khem@gmail.com>
+--- a/third_party/boringssl/BUILD.gn
++++ b/third_party/boringssl/BUILD.gn
+@@ -94,7 +94,7 @@ if (enable_rust_boringssl) {
+   }
+ }
+ 
+-if (is_msan) {
++if (is_msan || current_cpu == "arm64") {
+   # MSan instrumentation is incompatible with assembly optimizations.
+   # BoringSSL's GAS-compatible assembly knows how to detect MSan, but the NASM
+   # assembly does not, so we check for MSan explicitly.