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] epel10.2: refresh clang++-unknown-argument.patch
Date: Thu, 03 Sep 2026 07:49:22 GMT [thread overview]
Message-ID: <178842176214.1.10951162090335048713.rpms-chromium-030a043c1c47@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel10.2
Commit : 030a043c1c477aca339af2a7946c3f84c3ae01ea
Author : Than Ngo <than@redhat.com>
Date : 2026-09-03T08:11:46+07:00
Stats : +100/-68 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/030a043c1c477aca339af2a7946c3f84c3ae01ea?branch=epel10.2
Log:
refresh clang++-unknown-argument.patch
---
diff --git a/chromium-151-clang++-unknown-argument.patch b/chromium-151-clang++-unknown-argument.patch
deleted file mode 100644
index 9c3905c..0000000
--- a/chromium-151-clang++-unknown-argument.patch
+++ /dev/null
@@ -1,67 +0,0 @@
-Suppress warnings:
- clang diag: warning: unknown warning option '-Wno-unused-but-set-global'; did you mean '-Wno-unused-but-set-variable'? [-Wunknown-warning-option]
- clang diag: warning: unknown warning option '-Wno-unsafe-buffer-usage-in-static-sized-array'; did you mean '-Wno-unsafe-buffer-usage-in-container'? [-Wunknown-warning-option]
-
-diff -up chromium-151.0.7922.137/build/config/compiler/BUILD.gn.clang++-unknown-argument chromium-151.0.7922.137/build/config/compiler/BUILD.gn
---- chromium-151.0.7922.137/build/config/compiler/BUILD.gn.clang++-unknown-argument 2026-08-12 22:51:25.005846860 +0200
-+++ chromium-151.0.7922.137/build/config/compiler/BUILD.gn 2026-08-12 22:57:40.710373048 +0200
-@@ -576,14 +576,6 @@ config("compiler") {
- if (is_clang) {
- # Flags for diagnostics.
- cflags += [ "-fcolor-diagnostics" ]
-- if (!is_wasm) {
-- if (!is_win) {
-- cflags += [ "-fdiagnostics-show-inlining-chain" ]
-- } else {
-- # Combine after https://github.com/llvm/llvm-project/pull/192241
-- cflags += [ "/clang:-fdiagnostics-show-inlining-chain" ]
-- }
-- }
- if (diagnostics_print_source_range_info && !is_win) {
- cflags += [ "-fdiagnostics-print-source-range-info" ]
- }
-@@ -617,9 +609,6 @@ config("compiler") {
- # The performance improvement does not seem worth the risk. See
- # https://crbug.com/484082200 for background and https://crrev.com/c/7593035
- # for discussion.
-- if (!is_wasm) {
-- cflags += [ "-fno-lifetime-dse" ]
-- }
-
- # TODO(hans): Remove this once Clang generates better optimized debug info
- # by default. https://crbug.com/765793
-@@ -1563,12 +1552,7 @@ config("clang_warning_suppression") {
- ubsan_hardening("c_array_bounds") {
- sanitizer = "array-bounds"
- condition = !(is_asan && target_cpu == "x86") && !is_wasm
--
-- # Because we've enabled array-bounds sanitizing we also want to suppress
-- # the related warning about "unsafe-buffer-usage-in-static-sized-array",
-- # since we know that the array bounds sanitizing will catch any out-of-
-- # bounds accesses.
-- cflags = [ "-Wno-unsafe-buffer-usage-in-static-sized-array" ]
-+ cflags = [ ]
- }
-
- # Enable UBSan subset to ensure we always hit `return` statement in non-void
-@@ -1917,9 +1901,6 @@ config("default_warnings") {
- cflags += [
- # TODO(crbug.com/432275627): Fix and re-enable.
- "-Wno-uninitialized-const-pointer",
--
-- # TODO(crbug.com/495753203): Fix and re-enable.
-- "-Wno-unused-but-set-global",
- ]
- }
-
-diff -up chromium-151.0.7922.137/build/config/sanitizers/sanitizers.gni.clang++-unknown-argument chromium-151.0.7922.137/build/config/sanitizers/sanitizers.gni
---- chromium-151.0.7922.137/build/config/sanitizers/sanitizers.gni.clang++-unknown-argument 2026-08-11 00:27:27.000000000 +0200
-+++ chromium-151.0.7922.137/build/config/sanitizers/sanitizers.gni 2026-08-12 22:51:25.007516573 +0200
-@@ -540,7 +540,6 @@ template("ubsan_hardening") {
- # be usable even in release builds, i.e. as widely as possible.
- # It's important not to have full-on UBSan workarounds activate
- # just because we built support for a specific sanitizer.
-- "-fsanitize-ignore-for-ubsan-feature=${invoker.sanitizer}",
- ]
- if (defined(invoker.cflags)) {
- cflags += invoker.cflags
diff --git a/chromium-152-clang++-unknown-argument.patch b/chromium-152-clang++-unknown-argument.patch
new file mode 100644
index 0000000..0b87242
--- /dev/null
+++ b/chromium-152-clang++-unknown-argument.patch
@@ -0,0 +1,99 @@
+diff -up chromium-152.0.7977.75/build/config/compiler/BUILD.gn.clang++-unknown-argument chromium-152.0.7977.75/build/config/compiler/BUILD.gn
+--- chromium-152.0.7977.75/build/config/compiler/BUILD.gn.clang++-unknown-argument 2026-09-02 17:48:46.431579584 +0700
++++ chromium-152.0.7977.75/build/config/compiler/BUILD.gn 2026-09-02 17:48:46.437101551 +0700
+@@ -578,14 +578,6 @@ config("compiler") {
+ if (is_clang) {
+ # Flags for diagnostics.
+ cflags += [ "-fcolor-diagnostics" ]
+- if (!is_wasm) {
+- if (!is_win) {
+- cflags += [ "-fdiagnostics-show-inlining-chain" ]
+- } else {
+- # Combine after https://github.com/llvm/llvm-project/pull/192241
+- cflags += [ "/clang:-fdiagnostics-show-inlining-chain" ]
+- }
+- }
+ if (diagnostics_print_source_range_info && !is_win) {
+ cflags += [ "-fdiagnostics-print-source-range-info" ]
+ }
+@@ -619,9 +611,6 @@ config("compiler") {
+ # The performance improvement does not seem worth the risk. See
+ # https://crbug.com/484082200 for background and https://crrev.com/c/7593035
+ # for discussion.
+- if (!is_wasm) {
+- cflags += [ "-fno-lifetime-dse" ]
+- }
+
+ # TODO(hans): Remove this once Clang generates better optimized debug info
+ # by default. https://crbug.com/765793
+@@ -1581,12 +1570,7 @@ config("clang_warning_suppression") {
+ ubsan_hardening("c_array_bounds") {
+ sanitizer = "array-bounds"
+ condition = !(is_asan && target_cpu == "x86") && !is_wasm
+-
+- # Because we've enabled array-bounds sanitizing we also want to suppress
+- # the related warning about "unsafe-buffer-usage-in-static-sized-array",
+- # since we know that the array bounds sanitizing will catch any out-of-
+- # bounds accesses.
+- cflags = [ "-Wno-unsafe-buffer-usage-in-static-sized-array" ]
++ cflags = [ ]
+ }
+
+ # Enable UBSan subset to ensure we always hit `return` statement in non-void
+@@ -1935,9 +1919,6 @@ config("default_warnings") {
+ cflags += [
+ # TODO(crbug.com/432275627): Fix and re-enable.
+ "-Wno-uninitialized-const-pointer",
+-
+- # TODO(crbug.com/495753203): Fix and re-enable.
+- "-Wno-unused-but-set-global",
+ ]
+ }
+
+diff -up chromium-152.0.7977.75/build/config/sanitizers/sanitizers.gni.clang++-unknown-argument chromium-152.0.7977.75/build/config/sanitizers/sanitizers.gni
+--- chromium-152.0.7977.75/build/config/sanitizers/sanitizers.gni.clang++-unknown-argument 2026-09-01 05:47:51.000000000 +0700
++++ chromium-152.0.7977.75/build/config/sanitizers/sanitizers.gni 2026-09-02 17:48:46.438626395 +0700
+@@ -542,7 +542,6 @@ template("ubsan_hardening") {
+ # be usable even in release builds, i.e. as widely as possible.
+ # It's important not to have full-on UBSan workarounds activate
+ # just because we built support for a specific sanitizer.
+- "-fsanitize-ignore-for-ubsan-feature=${invoker.sanitizer}",
+ ]
+ if (defined(invoker.cflags)) {
+ cflags += invoker.cflags
+diff -up chromium-152.0.7977.75/third_party/dawn/src/utils/BUILD.gn.clang++-unknown-argument chromium-152.0.7977.75/third_party/dawn/src/utils/BUILD.gn
+--- chromium-152.0.7977.75/third_party/dawn/src/utils/BUILD.gn.clang++-unknown-argument 2026-09-01 05:47:51.000000000 +0700
++++ chromium-152.0.7977.75/third_party/dawn/src/utils/BUILD.gn 2026-09-02 17:48:46.439703484 +0700
+@@ -216,10 +216,6 @@ config("dawn_warnings") {
+ # -Wlifetime-safety-lifetimebound-violation) are not yet mapped to
+ # toggleable warning flags, so we suppress the entire group and disable
+ # the analysis pass.
+- "-Wno-lifetime-safety",
+- "-Wno-lifetime-safety-all",
+- "-Xclang=-fno-lifetime-safety-inference",
+- "-Xclang=-fno-experimental-lifetime-safety-tu-analysis",
+ ]
+
+ # P3. Checks that could be nice but probably don't help with hardening.
+diff -up chromium-152.0.7977.75/third_party/pdfium/BUILD.gn.clang++-unknown-argument chromium-152.0.7977.75/third_party/pdfium/BUILD.gn
+--- chromium-152.0.7977.75/third_party/pdfium/BUILD.gn.clang++-unknown-argument 2026-09-01 05:47:51.000000000 +0700
++++ chromium-152.0.7977.75/third_party/pdfium/BUILD.gn 2026-09-02 17:48:46.440379052 +0700
+@@ -183,7 +183,6 @@ config("pdfium_core_config") {
+ if (is_clang) {
+ cflags += [
+ "-Wcovered-switch-default",
+- "-Wlifetime-safety-permissive",
+ ]
+ }
+ }
+diff -up chromium-152.0.7977.75/third_party/skia/gn/skia/BUILD.gn.clang++-unknown-argument chromium-152.0.7977.75/third_party/skia/gn/skia/BUILD.gn
+--- chromium-152.0.7977.75/third_party/skia/gn/skia/BUILD.gn.clang++-unknown-argument 2026-09-01 05:47:51.000000000 +0700
++++ chromium-152.0.7977.75/third_party/skia/gn/skia/BUILD.gn 2026-09-02 17:48:46.440937850 +0700
+@@ -552,7 +552,6 @@ config("warnings") {
+ "-Wno-unused-member-function",
+ "-Wno-non-c-typedef-for-linkage", # Dawn, not Skia per se.
+
+- "-Wno-lifetime-safety",
+ "-Wno-lifetime-safety-suggestions",
+ "-Wno-lifetime-safety-validations",
+
diff --git a/chromium.spec b/chromium.spec
index bc6a92a..efc661c 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -406,7 +406,7 @@ Patch315: chromium-145-rustc-ftbfs.patch
# llvm <= 22
# clang++: error: unknown argument: '-fno-lifetime-dse'
# unknown warning option -Wno-nontrivial-memcall
-Patch316: chromium-151-clang++-unknown-argument.patch
+Patch316: chromium-152-clang++-unknown-argument.patch
Patch318: memory-allocator-dcheck-assert-fix.patch
reply other threads:[~2026-09-03 7:49 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=178842176214.1.10951162090335048713.rpms-chromium-030a043c1c47@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