public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105354] __builtin_shuffle for alignr generates suboptimal code unless SSSE3 is enabled Date: Thu, 28 Apr 2022 01:34:29 +0000 [thread overview] Message-ID: <bug-105354-4-qpHA68rnn4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105354-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105354 --- Comment #3 from Hongtao.liu <crazylht at gmail dot com> --- Created attachment 52893 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52893&action=edit Patch pending for GCC13 Now, we can also generate foo3: .LFB3: .cfi_startproc movdqa .LC1(%rip), %xmm2 pslldq $9, %xmm1 psrldq $5, %xmm0 pand %xmm2, %xmm0 pandn %xmm1, %xmm2 por %xmm2, %xmm0 ret .LC1: .byte -1 .byte -1 .byte -1 .byte -1 .byte -1 .byte -1 .byte -1 .byte -1 .byte -1 .byte -1 .byte 0 .byte 0 .byte 0 .byte 0 .byte 0 .byte 0 .align 16 for v16qi foo3 (v16qi a, v16qi b) { return __builtin_shufflevector (a, b, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17, 18, 19, 20, 21, 22); }
next prev parent reply other threads:[~2022-04-28 1:34 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-22 21:46 [Bug target/105354] New: " john_platts at hotmail dot com 2022-04-22 21:52 ` [Bug target/105354] " pinskia at gcc dot gnu.org 2022-04-24 3:38 ` crazylht at gmail dot com 2022-04-24 3:57 ` crazylht at gmail dot com 2022-04-28 1:34 ` crazylht at gmail dot com [this message] 2022-05-09 13:23 ` cvs-commit at gcc dot gnu.org 2022-05-09 13:27 ` crazylht at gmail dot com 2023-05-11 13:21 ` chfast at gmail 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-105354-4-qpHA68rnn4@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).