public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/115311] -fno-builtin-xxx allowing anything for xxx Date: Mon, 03 Jun 2024 06:57:39 +0000 [thread overview] Message-ID: <bug-115311-4-MfLUngTbTs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115311-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115311 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Note we handle -Wno-xyz similarly, but of course a typo like -fno-builtin-sun (s/sun/sin) isn't noticed this way which is the drawback.
prev parent reply other threads:[~2024-06-03 6:57 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-31 17:34 [Bug c/115311] New: " gjl at gcc dot gnu.org 2024-05-31 20:39 ` [Bug c/115311] " jsm28 at gcc dot gnu.org 2024-06-01 9:28 ` gjl at gcc dot gnu.org 2024-06-03 6:57 ` rguenth at gcc dot gnu.org [this message]
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-115311-4-MfLUngTbTs@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).