public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "plasmahh at gmx dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/103057] [11/12 Regression] Internal compiler error: Error reporting routines re-entered Date: Wed, 10 Nov 2021 15:17:28 +0000 [thread overview] Message-ID: <bug-103057-4-aGdBpDDKnX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103057-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103057 --- Comment #5 from Dennis Lubert <plasmahh at gmx dot net> --- Created attachment 51759 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51759&action=edit cvise generated compling testcase This one is pretty big but compiles with -w but ICEs without it. Differently to my original code, here there is no unused argument that when being used silences the warning and so circumvents the ICE. So I am not totally sure if there maybe a third bug lurking somewhere... Currently our code to be able to not ICE disables Wunused-parameter and Wunused-value for the functions in question.
next prev parent reply other threads:[~2021-11-10 15:17 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-03 13:00 [Bug c++/103057] New: " plasmahh at gmx dot net 2021-11-03 13:07 ` [Bug c++/103057] " marxin at gcc dot gnu.org 2021-11-03 13:09 ` marxin at gcc dot gnu.org 2021-11-03 13:49 ` plasmahh at gmx dot net 2021-11-07 7:30 ` [Bug c++/103057] [11/12 Regression] " pinskia at gcc dot gnu.org 2021-11-10 15:17 ` plasmahh at gmx dot net [this message] 2021-11-10 15:22 ` [Bug c++/103057] [11/12 Regression] Internal compiler error: Error reporting routines re-entered since r11-291-g0f50f6daa140186a marxin at gcc dot gnu.org 2022-01-17 13:01 ` rguenth at gcc dot gnu.org 2022-01-25 2:55 ` jason at gcc dot gnu.org 2022-01-26 4:23 ` cvs-commit at gcc dot gnu.org 2022-01-26 4:26 ` [Bug c++/103057] [11 " jason at gcc dot gnu.org 2022-01-26 5:01 ` jason at gcc dot gnu.org 2022-03-22 5:18 ` cvs-commit at gcc dot gnu.org 2022-04-12 17:29 ` jason 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-103057-4-aGdBpDDKnX@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).