public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/98849] [11 Regression] ICE in expand_shift_1, at expmed.c:2658 since g:7432f255b70811dafaf325d9403 Date: Wed, 27 Jan 2021 11:40:05 +0000 [thread overview] Message-ID: <bug-98849-4-iT38RY3rSB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98849-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98849 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- int a[1024], b[1024]; void foo (void) { for (int i = 0; i < 1024; i++) a[i] = b[i] << 3; } void bar (int x) { for (int i = 0; i < 1024; i++) a[i] = b[i] << x; } ICEs with -O3 -mcpu=iwmmxt too. Here the vectorizer understands the target has vector x vector shift and not vector x scalar, so we get: vect_cst__13 = { 3, 3 }; ... vect__2.7_14 = vect__1.6_8 << vect_cst__13; but veclower carelessly undoes that: vect__2.7_14 = vect__1.6_8 << 3;
next prev parent reply other threads:[~2021-01-27 11:40 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-27 9:00 [Bug target/98849] New: " marxin at gcc dot gnu.org 2021-01-27 9:00 ` [Bug target/98849] " marxin at gcc dot gnu.org 2021-01-27 11:28 ` jakub at gcc dot gnu.org 2021-01-27 11:40 ` jakub at gcc dot gnu.org [this message] 2021-01-27 13:06 ` jakub at gcc dot gnu.org 2021-01-27 13:28 ` jakub at gcc dot gnu.org 2021-01-27 13:34 ` jakub at gcc dot gnu.org 2021-01-27 13:37 ` ktkachov at gcc dot gnu.org 2021-01-27 13:38 ` clyon at gcc dot gnu.org 2021-01-27 13:39 ` clyon at gcc dot gnu.org 2021-01-27 13:40 ` jakub at gcc dot gnu.org 2021-01-27 13:44 ` jakub at gcc dot gnu.org 2021-01-27 15:51 ` jakub at gcc dot gnu.org 2021-01-27 18:00 ` clyon at gcc dot gnu.org 2021-01-28 15:57 ` jakub at gcc dot gnu.org 2021-01-29 10:55 ` cvs-commit at gcc dot gnu.org 2021-01-29 11:03 ` jakub 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-98849-4-iT38RY3rSB@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).