public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Than Ngo <than@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/chromium] epel9-next: Workaround for clang crash due to old clang-18.x on x86_64 el9/fedora40
Date: Fri, 07 Aug 2026 16:07:41 GMT	[thread overview]
Message-ID: <178611886188.1.16301735488955578119.rpms-chromium-c4b52ce1020e@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/chromium
Branch : epel9-next
Commit : c4b52ce1020e66badca8b730623a6aafe85481a1
Author : Than Ngo <than@redhat.com>
Date   : 2025-04-30T18:01:40+02:00
Stats  : +18/-1 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/chromium/c/c4b52ce1020e66badca8b730623a6aafe85481a1?branch=epel9-next

Log:
Workaround for clang crash due to old clang-18.x on x86_64 el9/fedora40

---
diff --git a/chromium-136-cnnpack-clang18-crash-x86_64.patch b/chromium-136-cnnpack-clang18-crash-x86_64.patch
new file mode 100644
index 0000000..f725834
--- /dev/null
+++ b/chromium-136-cnnpack-clang18-crash-x86_64.patch
@@ -0,0 +1,11 @@
+diff -up chromium-136.0.7103.59/third_party/xnnpack/BUILD.gn.than chromium-136.0.7103.59/third_party/xnnpack/BUILD.gn
+--- chromium-136.0.7103.59/third_party/xnnpack/BUILD.gn.than	2025-04-30 17:40:49.303107833 +0200
++++ chromium-136.0.7103.59/third_party/xnnpack/BUILD.gn	2025-04-30 17:51:06.934912263 +0200
+@@ -28,6 +28,7 @@ config("xnnpack_config") {
+   cflags = [
+     "-Wno-unused-function",
+     "-Wno-deprecated-comma-subscript",
++    "-O0",
+   ]
+ 
+   defines = [

diff --git a/chromium-latest.py b/chromium-latest.py
index dc94fd7..f8dddb4 100755
--- a/chromium-latest.py
+++ b/chromium-latest.py
@@ -358,6 +358,6 @@ if __name__ == '__main__':
   if (not args.prep):
     print("Compressing cleaned tree, please wait...")
     os.chdir(chromium_root_dir)
-    os.system("tar --exclude=\\.svn -cf - chromium-%s | xz -9 -T 0 -f > %s" % (chromium_version, chromium_clean_xz_file))
+    os.system("tar --exclude=\\.svn -cf - chromium-%s | xz -6 -T0 -f > %s" % (chromium_version, chromium_clean_xz_file))
 
   print("Finished!")

diff --git a/chromium.spec b/chromium.spec
index d7b35ff..08ec774 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -341,6 +341,9 @@ Patch315: chromium-134-rust-libadler2.patch
 # add -ftrivial-auto-var-init=zero and -fwrapv
 Patch316: chromium-122-clang-build-flags.patch
 
+# Workaround for clang crash due to old clang-18.x on x86_64 el9/fedora40
+Patch317: chromium-136-cnnpack-clang18-crash-x86_64.patch
+
 # Workaround for https://bugzilla.redhat.com/show_bug.cgi?id=2239523
 # https://bugs.chromium.org/p/chromium/issues/detail?id=1145581#c60
 # Disable BTI until this is fixed upstream.
@@ -1033,6 +1036,9 @@ Qt6 UI for chromium.
 %patch -P309 -p1 -b .el8-unsupport-rustc-flags
 %patch -P310 -p1 -b .el8-clang18-build-error
 %patch -P311 -p1 -b .clang18-template
+%ifarch x86_64
+%patch -P317 -p1 -b .xnnpack-clang18-crash-x86_64
+%endif
 %endif
 
 %patch -P312 -p1 -b .fstack-protector-strong

                 reply	other threads:[~2026-08-07 16:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178611886188.1.16301735488955578119.rpms-chromium-c4b52ce1020e@fedoraproject.org \
    --to=than@redhat.com \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox