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/94680] New: Missed optimization with __builtin_shuffle and zero vector Date: Tue, 21 Apr 2020 08:35:52 +0000 [thread overview] Message-ID: <bug-94680-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94680 Bug ID: 94680 Summary: Missed optimization with __builtin_shuffle and zero vector Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org Target Milestone: --- typedef float V __attribute__((vector_size(16))); typedef int VI __attribute__((vector_size(16))); V foo (V x) { return __builtin_shuffle (x, (V) { 0, 0, 0, 0 }, (VI) {0, 1, 4, 5}); } can be done using movq or vmovq in a single insn, rather than zeroing a register and doing movlhps.
next reply other threads:[~2020-04-21 8:35 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-21 8:35 jakub at gcc dot gnu.org [this message] 2020-04-21 8:38 ` [Bug target/94680] " jakub at gcc dot gnu.org 2021-04-21 0:38 ` pinskia at gcc dot gnu.org 2021-04-21 0:47 ` pinskia at gcc dot gnu.org 2021-04-21 8:59 ` crazylht at gmail dot com 2021-05-07 2:24 ` crazylht at gmail dot com 2021-05-13 0:42 ` cvs-commit at gcc dot gnu.org 2022-03-17 15:12 ` roger at nextmovesoftware dot com
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-94680-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).