public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gabravier at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104412] New: [Aarch64] Failure to optimize vector initialization from int64s Date: Sun, 06 Feb 2022 22:31:15 +0000 [thread overview] Message-ID: <bug-104412-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104412 Bug ID: 104412 Summary: [Aarch64] Failure to optimize vector initialization from int64s Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: gabravier at gmail dot com Target Milestone: --- #include <stdint.h> typedef int64_t v2i64 __attribute__((vector_size(16))); v2i64 _mm_set_epi64x(int64_t i1, int64_t i2) { union { int64_t data[2]; v2i64 v; } d = {.data = {i2, i1}}; return d.v; } With -O3, AArch64 GCC outputs this: _mm_set_epi64x(long, long): sub sp, sp, #16 stp x1, x0, [sp] ldr q0, [sp] add sp, sp, 16 ret LLVM instead outputs this: _mm_set_epi64x(long, long): fmov d0, x1 mov v0.d[1], x0 ret
next reply other threads:[~2022-02-06 22:31 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-06 22:31 gabravier at gmail dot com [this message] 2022-02-06 22:34 ` [Bug tree-optimization/104412] " pinskia at gcc dot gnu.org 2022-02-06 22:37 ` [Bug target/104412] union initialization of a vector is not optimized due to vector cost model pinskia at gcc dot gnu.org 2022-02-06 22:38 ` pinskia at gcc dot gnu.org 2022-02-07 9:02 ` rguenth 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-104412-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).