public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "haoxintu at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103219] New: [12 Regression] ICE Segmentation fault at -O3 (during GIMPLE pass: unrolljam) Date: Sat, 13 Nov 2021 02:21:26 +0000 [thread overview] Message-ID: <bug-103219-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103219 Bug ID: 103219 Summary: [12 Regression] ICE Segmentation fault at -O3 (during GIMPLE pass: unrolljam) Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: haoxintu at gmail dot com Target Milestone: --- Hi all. I am not sure whether there is a dup but it appears to be a recent regression issue. $cat small.c int a, b, c, e; int d[10]; int main() { if (c) if (f()) { g(); if (e) { a = 0; for (; a != 6; a = a + 2) { b = 0; for (; b <= 3; b++) d[b] &= 1; } } } return 0; } $gcc -w -O3 during GIMPLE pass: unrolljam small.c: In function ‘main’: small.c:3:5: internal compiler error: Segmentation fault 3 | int main() { | ^~~~ 0xc290af crash_signal ../../gcc/toplev.c:322 0x17bfea7 tree_loop_unroll_and_jam ../../gcc/gimple-loop-jam.c:596 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. $gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/media/haoxin/SeagateData/haoxin-data/dut-research/compilers/gcc/build/bin/../libexec/gcc/x86_64-pc-linux-gnu/12.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with:../configure --prefix=/home/haoxin/haoxin-data/dut-research/compilers/gcc/build/ --enable-bootstrap --enable-checking=release --enable-languages=c,c++ --enable-multilib Thread model: posix Supported LTO compression algorithms: zlib gcc version 12.0.0 20211112 (experimental) (GCC) Can also check here: https://godbolt.org/z/r7TKr8MxW Thanks, Haoxin
next reply other threads:[~2021-11-13 2:21 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-13 2:21 haoxintu at gmail dot com [this message] 2021-11-13 2:26 ` [Bug tree-optimization/103219] " pinskia at gcc dot gnu.org 2021-11-14 10:25 ` [Bug tree-optimization/103219] [12 Regression] ICE Segmentation fault at -O3 (during GIMPLE pass: unrolljam) since r12-4526-gd8edfadfc7a9795b aldyh at gcc dot gnu.org 2021-11-14 22:03 ` 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@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).