public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/98943] [11 Regression] gcc driver does not fail on unknown files: tricks configure scripts to recognize /W4 and -diag-disable 1,2,3,4 options Date: Wed, 03 Feb 2021 08:59:15 +0000 [thread overview] Message-ID: <bug-98943-4-s03IfXptV5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98943-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98943 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-02-03 CC| |jakub at gcc dot gnu.org, | |nathan at gcc dot gnu.org Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Haven't bisected, but just git blame tells me this is r11-6855-g4804de453e7f5f90dd5e64114abbd272f9e8f62d aka PR98452 change. I think we should reconsider that, perhaps limit to modules only or something.
next prev parent reply other threads:[~2021-02-03 8:59 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-02 20:18 [Bug driver/98943] New: " slyfox at gcc dot gnu.org 2021-02-03 7:36 ` [Bug driver/98943] [11 Regression] " rguenth at gcc dot gnu.org 2021-02-03 8:59 ` jakub at gcc dot gnu.org [this message] 2021-02-03 13:56 ` nathan at gcc dot gnu.org 2021-02-03 14:11 ` jakub at gcc dot gnu.org 2021-02-03 14:30 ` nathan at gcc dot gnu.org 2021-02-03 14:35 ` nathan at gcc dot gnu.org 2021-02-03 21:50 ` joseph at codesourcery dot com 2021-02-04 8:25 ` jakub at gcc dot gnu.org 2021-02-05 14:08 ` cvs-commit at gcc dot gnu.org 2021-02-05 14:09 ` nathan 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-98943-4-s03IfXptV5@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).