public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103094] New: [12 Regression] Incorrect codegen from AArch64 intrinsics Date: Fri, 05 Nov 2021 09:50:07 +0000 [thread overview] Message-ID: <bug-103094-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103094 Bug ID: 103094 Summary: [12 Regression] Incorrect codegen from AArch64 intrinsics Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: tnfchris at gcc dot gnu.org Target Milestone: --- Target: aarch64-* The following testcase --- #include <arm_neon.h> void foo (uint8x8x2_t cols_01_23, uint8x8x2_t cols_45_67, uint16_t* outptr0) { uint16x4x4_t cols_01_23_45_67 = { { vreinterpret_u16_u8(cols_01_23.val[0]), vreinterpret_u16_u8(cols_01_23.val[1]), vreinterpret_u16_u8(cols_45_67.val[0]), vreinterpret_u16_u8(cols_45_67.val[1]) } }; vst4_lane_u16(outptr0, cols_01_23_45_67, 0); } --- Causes incorrect codegen ``` foo: mov v4.8b, v0.8b mov v5.8b, v1.8b mov v6.8b, v1.8b mov v7.8b, v2.8b st4 {v4.h - v7.h}[0], [x0] ret ``` as the same register `v1` is used as source for two inputs. This happens in cprop_hardreg where a correct RTL ``` (insn 20 37 26 2 (set (reg:V4HI 61 v29 [ __val+8 ]) (reg:V4HI 36 v4 [ cols_01_23+8 ])) 1158 {*aarch64_simd_movv4hi} (nil)) ``` is turned into ``` (insn 20 37 26 2 (set (reg:V4HI 61 v29 [ __val+8 ]) (reg:V4HI 33 v1 [orig:36 cols_01_23+8 ] [36])) 1158 {*aarch64_simd_movv4hi} (nil)) ``` which is a bogus transform as `v1` is still live and pointing to `cols_45_67`. started somewhere between g:4096eb50d108a9ccef134f2e891c751b1cc9f6b2 and g:29a1af24eface3620e348be9429e7c2e872accbc
next reply other threads:[~2021-11-05 9:50 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-05 9:50 tnfchris at gcc dot gnu.org [this message] 2021-11-05 9:50 ` [Bug target/103094] " tnfchris at gcc dot gnu.org 2021-11-05 12:18 ` tnfchris at gcc dot gnu.org 2021-11-05 12:22 ` pinskia at gcc dot gnu.org 2021-11-05 12:29 ` tnfchris at gcc dot gnu.org 2021-11-06 5:50 ` pinskia at gcc dot gnu.org 2021-11-06 22:33 ` [Bug target/103094] [12 Regression] Incorrect codegen from uint8x8x2_t function arguments pinskia at gcc dot gnu.org 2021-12-13 9:12 ` [Bug target/103094] [12 Regression] AAPCS for new partial vector mode types (e.g. V2x8QI) are incorrect tnfchris at gcc dot gnu.org 2021-12-15 12:19 ` cvs-commit at gcc dot gnu.org 2021-12-15 12:24 ` rsandifo 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-103094-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).