public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/105151] New: [12 Regression] ICE in gimple_range_global, at value-query.cc:424
Date: Mon, 04 Apr 2022 16:45:37 +0000 [thread overview]
Message-ID: <bug-105151-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105151
Bug ID: 105151
Summary: [12 Regression] ICE in gimple_range_global, at
value-query.cc:424
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
Started between 20211121 and 20211128 :
$ cat z1.c
int __GIMPLE () foo ()
{
int _1;
return a_1(D);
}
$ gcc-12-20220403 -c z1.c -fgimple
z1.c: In function 'foo':
z1.c:4:10: error: anonymous SSA name cannot have default definition
4 | return a_1(D);
| ^~~
during GIMPLE pass: walloca
z1.c:1:17: internal compiler error: Segmentation fault
1 | int __GIMPLE () foo ()
| ^~~
0xe0a17f crash_signal
../../gcc/toplev.cc:322
0x1171d57 gimple_range_global(tree_node*)
../../gcc/value-query.cc:424
0x1bc9f4a ranger_cache::get_global_range(irange&, tree_node*) const
../../gcc/gimple-range-cache.cc:925
0x1bc5118 gimple_ranger::export_global_ranges()
../../gcc/gimple-range.cc:474
0x1c11061 pass_walloca::execute(function*)
../../gcc/gimple-ssa-warn-alloca.cc:381
next reply other threads:[~2022-04-04 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 16:45 gscfq@t-online.de [this message]
2022-04-05 6:59 ` [Bug c/105151] [12 Regression] ICE in gimple_range_global with invalid "gimple" language rguenth at gcc dot gnu.org
2022-04-05 7:16 ` 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@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).