public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109025] [13 Regression] ice in nested_in_vect_loop_p Date: Sun, 05 Mar 2023 00:40:46 +0000 [thread overview] Message-ID: <bug-109025-4-WGwaBLT7VE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109025-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109025 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note using &, | or ^ causes the ICE. Using + or - or * does not. Here is more simplified testcase: ``` int func_4(int t, int b) { for (int tt1 = 0; tt1 < 128 ; tt1 ++) { for (int tt = 0; tt < 128; tt ++) if (b) t |= 3; t |= 3; } return t; } ``` The above should just optimized to `return t | 3;` really. The ^/& case should be optimized too but it depends on if the number of loops is even or odd and if b was non-zero or not.
next prev parent reply other threads:[~2023-03-05 0:40 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-04 20:39 [Bug c/109025] New: " dcb314 at hotmail dot com 2023-03-04 20:42 ` [Bug c/109025] " dcb314 at hotmail dot com 2023-03-05 0:36 ` [Bug tree-optimization/109025] [13 Regression] " pinskia at gcc dot gnu.org 2023-03-05 0:36 ` pinskia at gcc dot gnu.org 2023-03-05 0:40 ` pinskia at gcc dot gnu.org [this message] 2023-03-05 8:33 ` dcb314 at hotmail dot com 2023-03-05 9:17 ` dcb314 at hotmail dot com 2023-03-05 9:32 ` dcb314 at hotmail dot com 2023-03-05 9:52 ` dcb314 at hotmail dot com 2023-03-05 10:17 ` dcb314 at hotmail dot com 2023-03-06 8:37 ` rguenth at gcc dot gnu.org 2023-03-06 9:41 ` rguenth at gcc dot gnu.org 2023-03-06 10:26 ` cvs-commit at gcc dot gnu.org 2023-03-06 10:37 ` 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-109025-4-WGwaBLT7VE@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).