public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102560] New: [12 Regression] g++.dg/Walloca1.C ICE with aggressive GC
Date: Sat, 02 Oct 2021 00:59:24 +0000 [thread overview]
Message-ID: <bug-102560-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102560
Bug ID: 102560
Summary: [12 Regression] g++.dg/Walloca1.C ICE with aggressive
GC
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: GC, ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: jason at gcc dot gnu.org
Target Milestone: ---
When I run make check-g++-strict-gc, which adds the flags
--param ggc-min-heapsize=0 --param ggc-min-expand=0
the compiler ICEs in Walloca1.C with
wa.ii: In function ‘void __static_initialization_and_destruction_0(int, int)’:
wa.ii:7:52: internal compiler error: Segmentation fault
7 | char *b = static_cast<char *>(__builtin_alloca (a));
| ^
0x176fa90 crash_signal
/home/jason/gt/gcc/toplev.c:331
0xacb5b2 contains_struct_check(tree_node const*, tree_node_structure_enum, char
const*, int, char const*)
/home/jason/gt/gcc/tree.h:3802
0xb64c70 wi::to_wide(tree_node const*)
/home/jason/gt/gcc/tree.h:6092
0x1bf0ce6 irange::irange_intersect(irange const&)
/home/jason/gt/gcc/value-range.cc:1684
0x1bf01fa irange::intersect(irange const*)
/home/jason/gt/gcc/value-range.cc:1514
0x1bea82b irange::intersect(irange const&)
/home/jason/gt/gcc/value-range.h:549
0x2bdd28d alloca_call_type
/home/jason/gt/gcc/gimple-ssa-warn-alloca.c:229
0x2bdd574 pass_walloca::execute(function*)
/home/jason/gt/gcc/gimple-ssa-warn-alloca.c:293
I don't get the same crash with my GCC 11 branch compiler.
next reply other threads:[~2021-10-02 0:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 0:59 jason at gcc dot gnu.org [this message]
2021-10-02 14:12 ` [Bug tree-optimization/102560] " pinskia at gcc dot gnu.org
2021-10-02 16:35 ` aldyh at gcc dot gnu.org
2021-10-02 16:48 ` aldyh at gcc dot gnu.org
2021-10-02 19:53 ` aldyh at gcc dot gnu.org
2021-10-03 17:51 ` aldyh at gcc dot gnu.org
2021-10-04 6:59 ` rguenth at gcc dot gnu.org
2021-10-04 6:59 ` rguenth at gcc dot gnu.org
2021-10-04 7:02 ` aldyh at gcc dot gnu.org
2021-10-04 11:20 ` cvs-commit at gcc dot gnu.org
2021-10-04 11:21 ` aldyh 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-102560-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).