public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "shaohua.li at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/110769] New: ICE in adjust_loop_info_after_peeling, at tree-ssa-loop-ivcanon.cc:1023 Date: Fri, 21 Jul 2023 15:04:56 +0000 [thread overview] Message-ID: <bug-110769-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110769 Bug ID: 110769 Summary: ICE in adjust_loop_info_after_peeling, at tree-ssa-loop-ivcanon.cc:1023 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: shaohua.li at inf dot ethz.ch Target Milestone: --- Looks like a recent regression. Compiler explorer: https://godbolt.org/z/eMh54dYKz $ cat a.c int a; int b(unsigned d) { int c = 0; for (; d; c++) d >>= 1; return c; } int main() { a = 0; for (; b(31) + a > 21; a = a + (unsigned)8) ; for (;;) ; } $ $ gcc-tk -O3 a.c during GIMPLE pass: ch_vect crash_0_reduced.c: In function ‘main’: crash_0_reduced.c:8:5: internal compiler error: in adjust_loop_info_after_peeling, at tree-ssa-loop-ivcanon.cc:1023 8 | int main() { | ^~~~ 0x216183e internal_error(char const*, ...) ???:0 0x9d1376 fancy_abort(char const*, int, char const*) ???:0 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. $ $ gcc-tk -v Using built-in specs. COLLECT_GCC=gcc-tk COLLECT_LTO_WRAPPER=/zdata/shaoli/compilers/ccbuilder-compilers/gcc-8cbdb2e4d64461d8a19e033bd33b585187059d8a/libexec/gcc/x86_64-pc-linux-gnu/14.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../configure --disable-multilib --disable-bootstrap --enable-languages=c,c++ --prefix=/zdata/shaoli/compilers/ccbuilder-compilers/gcc-8cbdb2e4d64461d8a19e033bd33b585187059d8a Thread model: posix Supported LTO compression algorithms: zlib gcc version 14.0.0 20230721 (experimental) (GCC) $
next reply other threads:[~2023-07-21 15:04 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-21 15:04 shaohua.li at inf dot ethz.ch [this message] 2023-07-21 20:36 ` [Bug tree-optimization/110769] " pinskia at gcc dot gnu.org 2023-07-23 2:39 ` zhendong.su at inf dot ethz.ch 2023-07-24 6:33 ` [Bug tree-optimization/110769] [14 Regression] " rguenth at gcc dot gnu.org 2023-07-30 15:01 ` shaohua.li at inf dot ethz.ch 2023-10-17 12:15 ` rguenth at gcc dot gnu.org 2023-11-03 12:27 ` [Bug tree-optimization/110769] [14 Regression] ICE in adjust_loop_info_after_peeling, at tree-ssa-loop-ivcanon.cc:1023 since r14-2674-gd0de3bf9175 shaohua.li at inf dot ethz.ch 2023-11-03 18:02 ` [Bug tree-optimization/110769] [14 Regression] ICE in adjust_loop_info_after_peeling, at tree-ssa-loop-ivcanon.cc:1023 since r14-2675-gef28aadad6e pinskia at gcc dot gnu.org 2024-01-11 13:53 ` rguenth at gcc dot gnu.org 2024-01-11 13:53 ` 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-110769-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).