public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106995] [13 Regression] ICE in expand_LOOP_VECTORIZED, at internal-fn.cc:2720 with -O2 since r13-1598-g0a7e721a6499a42f Date: Wed, 21 Sep 2022 08:29:00 +0000 [thread overview] Message-ID: <bug-106995-4-iRXO7Az5Ze@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106995-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106995 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-09-21 CC| |aldyh at redhat dot com, | |marxin at gcc dot gnu.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Summary|gcc-trunk crash at -O2 |[13 Regression] ICE in | |expand_LOOP_VECTORIZED, at | |internal-fn.cc:2720 with | |-O2 since | |r13-1598-g0a7e721a6499a42f --- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> --- Thanks for the report, please do not over-reduce test-cases so that it's full of warnings. Fixed test-case: $ cat pr106995.c int a, b, c, d; static unsigned long *e = &b, *f = &b; int g(int h) { return a >= 2 ? 0 : h >> a; } void i() { for (; c;) { if (*f ^ 11) for (;;) ; d = g(0 >= 0); *e = d; } } int main() {} Started with r13-1598-g0a7e721a6499a42f.
next prev parent reply other threads:[~2022-09-21 8:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-21 7:59 [Bug c/106995] New: gcc-trunk crash at -O2 shaohua.li at inf dot ethz.ch 2022-09-21 8:14 ` [Bug tree-optimization/106995] " shaohua.li at inf dot ethz.ch 2022-09-21 8:29 ` marxin at gcc dot gnu.org [this message] 2022-09-21 8:29 ` [Bug tree-optimization/106995] [13 Regression] ICE in expand_LOOP_VECTORIZED, at internal-fn.cc:2720 with -O2 since r13-1598-g0a7e721a6499a42f marxin at gcc dot gnu.org 2022-09-21 9:19 ` rguenth at gcc dot gnu.org 2022-10-18 8:42 ` rguenth at gcc dot gnu.org 2022-11-29 11:59 ` cvs-commit at gcc dot gnu.org 2022-11-29 11:59 ` 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-106995-4-iRXO7Az5Ze@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).