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 target/103094] [12 Regression] Incorrect codegen from AArch64 intrinsics Date: Sat, 06 Nov 2021 05:50:39 +0000 [thread overview] Message-ID: <bug-103094-4-B6lA0D5t0C@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103094-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103094 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-11-06 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW See Also|https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=101529 | CC| |pinskia at gcc dot gnu.org --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- What is wrong rather not understanding the incoming arguments is passed as q0 rather than d0/d1. (insn 2 6 3 2 (set (reg/v:V2x8QI 101 [ cols_01_23 ]) (reg:V2x8QI 32 v0 [ cols_01_23 ])) "t66.c":5:1 -1 (nil)) (insn 3 2 4 2 (set (reg/v:V2x8QI 102 [ cols_45_67 ]) (reg:V2x8QI 33 v1 [ cols_45_67 ])) "t66.c":5:1 -1 (nil)) Caused by r12-4912-geb04ccf4bfd6586 .
next prev parent reply other threads:[~2021-11-06 5:50 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-05 9:50 [Bug target/103094] New: " tnfchris at gcc dot gnu.org 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 [this message] 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-B6lA0D5t0C@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).