public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mjires at suse dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113442] New: [14 Regression] ICE in compute_live_loop_exits, at tree-ssa-loop-manip.cc:250 since r14-7195-g411de96dbf2bda Date: Wed, 17 Jan 2024 13:37:09 +0000 [thread overview] Message-ID: <bug-113442-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113442 Bug ID: 113442 Summary: [14 Regression] ICE in compute_live_loop_exits, at tree-ssa-loop-manip.cc:250 since r14-7195-g411de96dbf2bda Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: mjires at suse dot cz CC: tamar.christina at arm dot com Target Milestone: --- Compiling reduced testcase g++.dg/torture/predcom-1.C results in ICE since r14-7195-g411de96dbf2bda. $ cat predcom-1.C struct Foo { int *ptr; }; bool Baz(Foo first) { while (first.ptr) if (*first.ptr++) return false; } $ g++ predcom-1.C -fno-tree-sra -O3 -mavx512bf16 predcom-1.C: In function ‘bool Baz(Foo)’: predcom-1.C:8:1: warning: control reaches end of non-void function [-Wreturn-type] 8 | } | ^ during GIMPLE pass: vect predcom-1.C:4:6: internal compiler error: in compute_live_loop_exits, at tree-ssa-loop-manip.cc:250 4 | bool Baz(Foo first) { | ^~~ 0x1cf88f5 compute_live_loop_exits /home/mjires/git/GCC/master/gcc/tree-ssa-loop-manip.cc:250 0x1cf8cf1 add_exit_phis_var /home/mjires/git/GCC/master/gcc/tree-ssa-loop-manip.cc:332 0x1cf90b4 add_exit_phis /home/mjires/git/GCC/master/gcc/tree-ssa-loop-manip.cc:392 0x1cf970a rewrite_into_loop_closed_ssa_1 /home/mjires/git/GCC/master/gcc/tree-ssa-loop-manip.cc:606 0x1cf977b rewrite_into_loop_closed_ssa(bitmap_head*, unsigned int) /home/mjires/git/GCC/master/gcc/tree-ssa-loop-manip.cc:628 0x1eaec75 execute /home/mjires/git/GCC/master/gcc/tree-vectorizer.cc:1360 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. $ g++ -v Using built-in specs. COLLECT_GCC=g++ COLLECT_LTO_WRAPPER=/home/mjires/built/master/libexec/gcc/x86_64-pc-linux-gnu/14.0.1/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /home/mjires/git/GCC/master/configure --prefix=/home/mjires/built/master --disable-bootstrap --enable-languages=c,c++,fortran,lto --disable-multilib --disable-libsanitizer --enable-checking : (reconfigured) /home/mjires/git/GCC/master/configure --prefix=/home/mjires/built/master --disable-bootstrap --enable-languages=c,c++,fortran,lto --disable-multilib --disable-libsanitizer --enable-checking Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 14.0.1 20240117 (experimental) (GCC)
next reply other threads:[~2024-01-17 13:37 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-17 13:37 mjires at suse dot cz [this message] 2024-01-17 14:23 ` [Bug tree-optimization/113442] " rguenth at gcc dot gnu.org 2024-01-19 9:49 ` 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-113442-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).