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/95967] Poor aarch64 vector constructor code when using arm_neon.h Date: Thu, 12 Aug 2021 07:37:57 +0000 [thread overview] Message-ID: <bug-95967-4-FpoK5LeYgF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95967-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95967 Tamar Christina <tnfchris at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tnfchris at gcc dot gnu.org --- Comment #6 from Tamar Christina <tnfchris at gcc dot gnu.org> --- f3 and g3 no longer use the stack: f3: ins v0.s[1], v1.s[0] sub sp, sp, #16 add sp, sp, 16 ins v0.s[2], v2.s[0] ins v0.s[3], v3.s[0] ret g3: ldr s0, [x0] sub sp, sp, #16 ld1 {v0.s}[1], [x1] ld1 {v0.s}[2], [x2] ld1 {v0.s}[3], [x3] add sp, sp, 16 ret Though we still allocate the space for it (but that's a general AArch64 issue). for the other cases the only thing left is the initializations.
next prev parent reply other threads:[~2021-08-12 7:37 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-29 15:20 [Bug target/95967] New: " rsandifo at gcc dot gnu.org 2020-06-29 15:21 ` [Bug target/95967] " rsandifo at gcc dot gnu.org 2021-05-30 23:08 ` pinskia at gcc dot gnu.org 2021-05-30 23:10 ` pinskia at gcc dot gnu.org 2021-05-30 23:13 ` pinskia at gcc dot gnu.org 2021-05-30 23:19 ` pinskia at gcc dot gnu.org 2021-06-03 0:46 ` pinskia at gcc dot gnu.org 2021-08-12 7:37 ` tnfchris at gcc dot gnu.org [this message] 2023-05-12 6:06 ` pinskia 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-95967-4-FpoK5LeYgF@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).