public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/114314] ICE: in common_handle_option, at opts.cc:3356 with -fno-multiflags
Date: Tue, 12 Mar 2024 04:00:15 +0000 [thread overview]
Message-ID: <bug-114314-4-pJPmsqOMt1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114314-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114314
--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>:
https://gcc.gnu.org/g:c4e5789cede6974b6483c0f82069ff80b5a547e4
commit r14-9434-gc4e5789cede6974b6483c0f82069ff80b5a547e4
Author: Andrew Pinski <quic_apinski@quicinc.com>
Date: Mon Mar 11 17:40:08 2024 -0700
Reject -fno-multiflags [PR114314]
When -fmultiflags option support was added in r13-3693-g6b1a2474f9e422,
it accidently allowed -fno-multiflags which then would pass on to cc1.
This fixes that oversight.
Committed as obvious after bootstrap/test on x86_64-linux-gnu.
gcc/ChangeLog:
PR driver/114314
* common.opt (fmultiflags): Add RejectNegative.
Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>
next prev parent reply other threads:[~2024-03-12 4:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 23:04 [Bug c/114314] New: [14 Regression] " patrick at rivosinc dot com
2024-03-11 23:13 ` [Bug driver/114314] " pinskia at gcc dot gnu.org
2024-03-12 0:38 ` pinskia at gcc dot gnu.org
2024-03-12 0:39 ` pinskia at gcc dot gnu.org
2024-03-12 4:00 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-12 4:02 ` cvs-commit at gcc dot gnu.org
2024-03-12 4:02 ` pinskia 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-114314-4-pJPmsqOMt1@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).