public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103219] [12 Regression] ICE Segmentation fault at -O3 (during GIMPLE pass: unrolljam) since r12-4526-gd8edfadfc7a9795b
Date: Sun, 14 Nov 2021 10:25:02 +0000 [thread overview]
Message-ID: <bug-103219-4-H8dBDaoIs1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103219-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103219
Aldy Hernandez <aldyh at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-11-14
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #1 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
Looks like a latent bug elsewhere as we're not threading anything. For that
matter, test fails even with -fno-thread-jumps.
$ ./cc1 a.c -O3 -fno-thread-jumps -quiet -w
during GIMPLE pass: unrolljam
a.c: In function ‘main’:
a.c:3:5: internal compiler error: Segmentation fault
3 | int main() {
| ^~~~
0x133a4fb crash_signal
Seems like tree_loop_unroll_and_jam is dereferencing a null return from
single_dom_exit():
auto_bitmap exit_bbs;
bitmap_set_bit (exit_bbs, single_dom_exit (outer)->dest->index);
todo |= do_rpo_vn (cfun, loop_preheader_edge (outer), exit_bbs);
(gdb) p debug(outer)
loop_1 (header = 9, latch = 26, niter = )
$6 = void
(gdb) p single_dom_exit (outer)
$7 = <edge 0x0>
next prev parent reply other threads:[~2021-11-14 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 2:21 [Bug tree-optimization/103219] New: [12 Regression] ICE Segmentation fault at -O3 (during GIMPLE pass: unrolljam) haoxintu at gmail dot com
2021-11-13 2:26 ` [Bug tree-optimization/103219] " pinskia at gcc dot gnu.org
2021-11-14 10:25 ` aldyh at gcc dot gnu.org [this message]
2021-11-14 22:03 ` [Bug tree-optimization/103219] [12 Regression] ICE Segmentation fault at -O3 (during GIMPLE pass: unrolljam) since r12-4526-gd8edfadfc7a9795b pinskia at gcc dot gnu.org
2021-11-15 8:57 ` rguenth at gcc dot gnu.org
2021-11-15 10:10 ` cvs-commit at gcc dot gnu.org
2021-11-15 10:11 ` [Bug tree-optimization/103219] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-02-17 8:20 ` [Bug tree-optimization/103219] [12 " 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-103219-4-H8dBDaoIs1@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).