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/105151] [12 Regression] ICE in gimple_range_global with invalid "gimple" language
Date: Tue, 05 Apr 2022 06:59:28 +0000 [thread overview]
Message-ID: <bug-105151-4-Er6WFOWwMX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105151-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105151
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
CC| |aldyh at gcc dot gnu.org
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0 |1
Last reconfirmed| |2022-04-05
Blocks| |101057
Target Milestone|--- |12.0
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
going down passes after errors is always tricky - we do stop but it seems the
diagnostic passes are still run because they are part of "lowering"
(why is pass_walloca not in pass_build_ssa_passes like
pass_warn_{printf,nonnull_compare,access}?). In particular it seems to look
at ranger but we are not even in SSA form!?
ranger "support" was added with r12-1078-gfe9a499cb8775c which should have
moved the pass to a place where we are in SSA form or the ranger use
restricted to the late pass.
I'm testing moving of the pass.
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-04-05 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 16:45 [Bug c/105151] New: [12 Regression] ICE in gimple_range_global, at value-query.cc:424 gscfq@t-online.de
2022-04-05 6:59 ` rguenth at gcc dot gnu.org [this message]
2022-04-05 7:16 ` [Bug c/105151] [12 Regression] ICE in gimple_range_global with invalid "gimple" language aldyh at gcc dot gnu.org
2022-04-05 7:55 ` cvs-commit at gcc dot gnu.org
2022-04-05 7:55 ` rguenth 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-105151-4-Er6WFOWwMX@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).