From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: /, bin/install-qa-check.d/
Date: Wed, 9 Nov 2022 07:39:30 +0000 (UTC) [thread overview]
Message-ID: <1667979533.739e8de006c6c2a247edef3e616fcdecba28edc8.sam@gentoo> (raw)
commit: 739e8de006c6c2a247edef3e616fcdecba28edc8
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 9 07:38:53 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Nov 9 07:38:53 2022 +0000
URL: https://gitweb.gentoo.org/proj/portage.git/commit/?id=739e8de0
install-qa-check.d/90gcc-warnings: drop some conversion warnings for now
While I want to keep these, Bash triggers them with a trick it uses
to force truncation in random.c, and I can't really justify FEATURES=stricter
stopping Bash from installing.
Signed-off-by: Sam James <sam <AT> gentoo.org>
NEWS | 4 ----
bin/install-qa-check.d/90gcc-warnings | 13 +++++++++----
2 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/NEWS b/NEWS
index 5ee6e3bd1..2480f55a8 100644
--- a/NEWS
+++ b/NEWS
@@ -30,10 +30,6 @@ Features:
* -Wincompatible-function-pointer-types (Clang, becomes fatal in Clang 16)
(note we already have -Wincompatible-pointer-types in the list for GCC)
* -Wundefined-reinterpret-cast (Clang, C++ strict aliasing)
- * -Wint-conversion
- * -Wint-to-pointer-cast
- * -Wpointer-to-int-cast
- * -Wint-to-void-pointer-cast
* -Wcast-function-type-strict (Clang, CFI)
* Further -Wformat matches for missing specifiers.
In future, we may warn on all -Wformat (in particular because of e.g.
diff --git a/bin/install-qa-check.d/90gcc-warnings b/bin/install-qa-check.d/90gcc-warnings
index 845a83b08..7a27b5aaa 100644
--- a/bin/install-qa-check.d/90gcc-warnings
+++ b/bin/install-qa-check.d/90gcc-warnings
@@ -66,14 +66,19 @@ gcc_warn_check() {
# the address of ... will never be NULL and likes
# (uses of function refs & string constants in conditionals)
'warning: .*\[-Waddress\]'
+
+ # TODO: we want to enable these but bash currently triggers
+ # them with a trick in random.c where it intentionally wants
+ # some truncation :(
+ #
# warning: assignment/initialization to ... from ... makes integer from pointer without cast
- 'warning: .*\[-Wint-conversion\]'
+ #'warning: .*\[-Wint-conversion\]'
# warning: cast to ... from integer of different size (or smaller size)
- 'warning: .*\[-Wint-to-pointer-cast\]'
+ #'warning: .*\[-Wint-to-pointer-cast\]'
# warning: cast to ... from (smaller) integer type
- 'warning: .*\[-Wint-to-void-pointer-cast\]'
+ #'warning: .*\[-Wint-to-void-pointer-cast\]'
# warning: cast from ... to integer of different size
- 'warning: .*\[-Wpointer-to-int-cast\]'
+ #'warning: .*\[-Wpointer-to-int-cast\]'
# -Wformat
# TODO: comment out some time in future for time_t & LFS preparedness
next reply other threads:[~2022-11-09 7:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 7:39 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-25 8:15 [gentoo-commits] proj/portage:master commit in: /, bin/install-qa-check.d/ Sam James
2023-04-07 10:41 Sam James
2022-11-20 23:33 Sam James
2022-11-09 7:30 Sam James
2022-11-09 3:38 Sam James
2022-11-09 3:31 Sam James
2022-08-23 0:33 Sam James
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=1667979533.739e8de006c6c2a247edef3e616fcdecba28edc8.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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