public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108310] Some warnings that -Wtraditional-conversion causes to be emitted aren't actually controlled by it Date: Fri, 06 Jan 2023 04:06:06 +0000 [thread overview] Message-ID: <bug-108310-4-fT7b9l4XQh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108310-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108310 Eric Gallager <egallager at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=103210 Blocks| |44209 --- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> --- Kinda related to bug 103210, IMO, in that I've uncovered both of them by building my fork of gdb with gcc: https://github.com/cooljeanius/apple-gdb-1824 And, they're also both examples of places where warnings in gcc/c/c-typeck.cc have a "0" for the second argument where they really ought to have an option name instead, as per bug 44209. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 [Bug 44209] [meta-bug] Some warnings are not linked to diagnostics options
next prev parent reply other threads:[~2023-01-06 4:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-06 3:59 [Bug c/108310] New: " egallager at gcc dot gnu.org 2023-01-06 4:06 ` egallager at gcc dot gnu.org [this message] 2023-01-06 4:16 ` [Bug c/108310] " egallager at gcc dot gnu.org 2023-01-12 14:59 ` egallager at gcc dot gnu.org 2023-01-12 15:13 ` redi at gcc dot gnu.org 2023-08-07 22:28 ` egallager at gcc dot gnu.org 2023-08-25 13:34 ` egallager at gcc dot gnu.org
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=bug-108310-4-fT7b9l4XQh@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).