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/107305] ICE: 'verify_gimple' failed Date: Wed, 19 Oct 2022 07:16:33 +0000 [thread overview] Message-ID: <bug-107305-4-cyUb0Su1BI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107305-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107305 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |error-recovery, | |ice-on-invalid-code Blocks| |101057 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- Yeah, the "design" of the GIMPLE frontend is that most IL validation is done by the verifiers instead of the parser. Maybe we can run the verifier on the parsing result and abort compilation if there was any error. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101057 [Bug 101057] [gimplefe] GIMPLE frontend issues
next prev parent reply other threads:[~2022-10-19 7:16 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-18 17:41 [Bug c/107305] New: " gscfq@t-online.de 2022-10-18 17:43 ` [Bug c/107305] " mpolacek at gcc dot gnu.org 2022-10-18 17:44 ` pinskia at gcc dot gnu.org 2022-10-19 6:47 ` marxin at gcc dot gnu.org 2022-10-19 7:16 ` rguenth at gcc dot gnu.org [this message] 2022-10-20 9:29 ` cvs-commit at gcc dot gnu.org 2022-10-20 9:31 ` rguenth at gcc dot gnu.org 2022-11-28 22:21 ` 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-107305-4-cyUb0Su1BI@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).