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/99593] [11 Regression] arm Neon ICE when compiling firefox (skia) since r11-6708 Date: Mon, 15 Mar 2021 10:29:11 +0000 [thread overview] Message-ID: <bug-99593-4-i5U92NQN6v@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99593-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99593 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I've tried to reproduce it with typedef __simd128_int32_t int32x4_t; void foo (int32x4_t c) { int32x4_t b = __builtin_neon_vdup_nv4si (3); register int32x4_t a __asm ("d16"); asm volatile ("" : "=w" (a)); a = a >> b; a |= c; asm volatile ("" : : "w" (a)); } but it doesn't, for some reason the ICE needs a REG_EQUAL attribute on the right shift into which we propagate the constant and LRA picks the constant from there, but haven't managed to force that.
next prev parent reply other threads:[~2021-03-15 10:29 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-15 9:40 [Bug target/99593] New: [11 Regression] arm MVE " jakub at gcc dot gnu.org 2021-03-15 9:54 ` [Bug target/99593] " jakub at gcc dot gnu.org 2021-03-15 10:00 ` [Bug target/99593] [11 Regression] arm Neon " ktkachov at gcc dot gnu.org 2021-03-15 10:29 ` jakub at gcc dot gnu.org [this message] 2021-03-15 13:54 ` clyon at gcc dot gnu.org 2021-03-15 13:59 ` jakub at gcc dot gnu.org 2021-03-15 14:08 ` jakub at gcc dot gnu.org 2021-03-17 17:17 ` clyon at gcc dot gnu.org 2021-03-17 17:21 ` ktkachov at gcc dot gnu.org 2021-03-17 17:23 ` jakub at gcc dot gnu.org 2021-03-17 18:54 ` ktkachov at gcc dot gnu.org 2021-03-17 19:18 ` jakub at gcc dot gnu.org 2021-03-17 19:51 ` clyon at gcc dot gnu.org 2021-03-17 20:11 ` jakub at gcc dot gnu.org 2021-03-18 12:22 ` clyon at gcc dot gnu.org 2021-03-19 12:49 ` cvs-commit at gcc dot gnu.org 2021-03-19 12:50 ` jakub at gcc dot gnu.org 2021-03-19 12:51 ` jakub at gcc dot gnu.org 2021-03-19 12:59 ` clyon at gcc dot gnu.org 2021-03-23 15:30 ` cvs-commit 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-99593-4-i5U92NQN6v@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).