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] f43: - Suppress linker_messages Warnings in Rust and other warnings
Date: Wed, 12 Aug 2026 21:12:39 GMT [thread overview]
Message-ID: <178656915926.1.15611267850762499766.rpms-chromium-1530553430fc@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : f43
Commit : 1530553430fcfc2c26aa7e69a9e924fb61ecb2a8
Author : Than Ngo <than@redhat.com>
Date : 2026-08-12T23:09:17+02:00
Stats : +35/-13 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/1530553430fcfc2c26aa7e69a9e924fb61ecb2a8?branch=f43
Log:
- Suppress linker_messages Warnings in Rust and other warnings
---
diff --git a/chromium-151-clang++-unknown-argument.patch b/chromium-151-clang++-unknown-argument.patch
index 9484481..9c3905c 100644
--- a/chromium-151-clang++-unknown-argument.patch
+++ b/chromium-151-clang++-unknown-argument.patch
@@ -1,6 +1,10 @@
-diff -up chromium-151.0.7922.47/build/config/compiler/BUILD.gn.me chromium-151.0.7922.47/build/config/compiler/BUILD.gn
---- chromium-151.0.7922.47/build/config/compiler/BUILD.gn.me 2026-07-23 11:54:01.269128807 +0200
-+++ chromium-151.0.7922.47/build/config/compiler/BUILD.gn 2026-07-23 11:58:32.694584084 +0200
+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.
@@ -26,18 +30,33 @@ diff -up chromium-151.0.7922.47/build/config/compiler/BUILD.gn.me chromium-151.0
# TODO(hans): Remove this once Clang generates better optimized debug info
# by default. https://crbug.com/765793
-@@ -1925,8 +1914,6 @@ config("default_warnings") {
- # TODO(crbug.com/40284799): Fix and re-enable.
- "-Wno-thread-safety-reference-return",
+@@ -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 = [ ]
+ }
-- # TODO(crbug.com/376641662): Fix and re-enable.
-- "-Wno-nontrivial-memcall",
- ]
+ # 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",
+ ]
+ }
- if (!is_wasm) {
-diff -up chromium-151.0.7922.47/build/config/sanitizers/sanitizers.gni.me chromium-151.0.7922.47/build/config/sanitizers/sanitizers.gni
---- chromium-151.0.7922.47/build/config/sanitizers/sanitizers.gni.me 2026-07-23 11:56:11.855123098 +0200
-+++ chromium-151.0.7922.47/build/config/sanitizers/sanitizers.gni 2026-07-23 11:56:26.260247113 +0200
+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
diff --git a/chromium.spec b/chromium.spec
index 061e0df..ce55ce7 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -1354,6 +1354,9 @@ export CFLAGS
export CXXFLAGS
export LDFLAGS
+# Suppress linker_messages Warnings in Rust
+export RUSTFLAGS="-A linker_messages"
+
# need for error: the option `Z` is only accepted on the nightly compiler
export RUSTC_BOOTSTRAP=1
reply other threads:[~2026-08-12 21:12 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=178656915926.1.15611267850762499766.rpms-chromium-1530553430fc@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