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 tree-optimization/98856] [11 Regression] botan AES-128/XTS is slower by ~17% since r11-6649-g285fa338b06b804e72997c4d876ecf08a9c083af Date: Fri, 05 Feb 2021 19:48:35 +0000 [thread overview] Message-ID: <bug-98856-4-rchDEQiJsN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98856-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98856 --- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The needed permutations for this boil down to typedef int V __attribute__((vector_size (16))); typedef int W __attribute__((vector_size (32))); #ifdef __clang__ V f1 (V x) { return __builtin_shufflevector (x, x, 1, 1, 3, 3); } V f2 (V x, V y) { return __builtin_shufflevector (x, y, 1, 5, 3, 7); } V f3 (V x, V y) { return __builtin_shufflevector (x, y, 0, 5, 2, 7); } #ifdef __AVX2__ W f4 (W x, W y) { return __builtin_shufflevector (x, y, 1, 9, 3, 11, 5, 13, 7, 15); } W f5 (W x, W y) { return __builtin_shufflevector (x, y, 0, 9, 2, 11, 4, 13, 6, 15); } W f6 (W x) { return __builtin_shufflevector (x, x, 1, 1, 3, 3, 5, 5, 7, 7); } #endif V f7 (V x) { return __builtin_shufflevector (x, x, 1, 3, 2, 3); } V f8 (V x) { return __builtin_shufflevector (x, x, 0, 2, 2, 3); } V f9 (V x, V y) { return __builtin_shufflevector (x, y, 0, 4, 1, 5); } #else V f1 (V x) { return __builtin_shuffle (x, (V) { 1, 1, 3, 3 }); } V f2 (V x, V y) { return __builtin_shuffle (x, y, (V) { 1, 5, 3, 7 }); } V f3 (V x, V y) { return __builtin_shuffle (x, y, (V) { 0, 5, 2, 7 }); } #ifdef __AVX2__ W f4 (W x, W y) { return __builtin_shuffle (x, y, (W) { 1, 9, 3, 11, 5, 13, 7, 15 }); } W f5 (W x, W y) { return __builtin_shuffle (x, y, (W) { 0, 9, 2, 11, 4, 13, 6, 15 }); } W f6 (W x, W y) { return __builtin_shuffle (x, (W) { 1, 1, 3, 3, 5, 5, 7, 7 }); } #endif V f7 (V x) { return __builtin_shuffle (x, (V) { 1, 3, 2, 3 }); } V f8 (V x) { return __builtin_shuffle (x, (V) { 0, 2, 2, 3 }); } V f9 (V x, V y) { return __builtin_shuffle (x, y, (V) { 0, 4, 1, 5 }); } #endif With -msse2, LLVM emits 2 x pshufd $237 + punpckldq for f2 and pshufd $237 + pshufd $232 + punpckldq, we give up or emit very large code. With -msse4, we handle everything, and f1/f3 are the same/comparable, but for f2 we emit 2 x pshufb (with memory operands) + por while LLVM emits pshufd $245 + pblendw $204. With -mavx2, the f2 inefficiency remains, and for f4 we emit 2x vpshufb with memory operands + vpor while LLVM emits vpermilps $245 + vblendps $170. f6-f9 are all insns that we handle through a single insn and that plus f3 are the roadblocks to build the f2 and f4 permutations more efficiently.
next prev parent reply other threads:[~2021-02-05 19:48 UTC|newest] Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-27 14:28 [Bug tree-optimization/98856] New: " marxin at gcc dot gnu.org 2021-01-27 14:29 ` [Bug tree-optimization/98856] " marxin at gcc dot gnu.org 2021-01-27 14:44 ` rguenth at gcc dot gnu.org 2021-01-28 7:47 ` rguenth at gcc dot gnu.org 2021-01-28 8:44 ` marxin at gcc dot gnu.org 2021-01-28 9:40 ` rguenth at gcc dot gnu.org 2021-01-28 11:03 ` rguenth at gcc dot gnu.org 2021-01-28 11:19 ` rguenth at gcc dot gnu.org 2021-01-28 11:57 ` rguenth at gcc dot gnu.org 2021-02-05 10:18 ` rguenth at gcc dot gnu.org 2021-02-05 11:52 ` jakub at gcc dot gnu.org 2021-02-05 12:52 ` rguenth at gcc dot gnu.org 2021-02-05 13:43 ` jakub at gcc dot gnu.org 2021-02-05 14:36 ` jakub at gcc dot gnu.org 2021-02-05 16:29 ` jakub at gcc dot gnu.org 2021-02-05 17:55 ` jakub at gcc dot gnu.org 2021-02-05 19:48 ` jakub at gcc dot gnu.org [this message] 2021-02-08 15:14 ` jakub at gcc dot gnu.org 2021-03-04 12:14 ` rguenth at gcc dot gnu.org 2021-03-04 15:36 ` rguenth at gcc dot gnu.org 2021-03-04 16:12 ` rguenth at gcc dot gnu.org 2021-03-04 17:56 ` ubizjak at gmail dot com 2021-03-04 18:12 ` ubizjak at gmail dot com 2021-03-05 7:44 ` rguenth at gcc dot gnu.org 2021-03-05 7:46 ` rguenth at gcc dot gnu.org 2021-03-05 8:29 ` ubizjak at gmail dot com 2021-03-05 10:04 ` rguenther at suse dot de 2021-03-05 10:43 ` rguenth at gcc dot gnu.org 2021-03-05 11:56 ` ubizjak at gmail dot com 2021-03-05 12:25 ` ubizjak at gmail dot com 2021-03-05 12:27 ` rguenth at gcc dot gnu.org 2021-03-05 12:49 ` jakub at gcc dot gnu.org 2021-03-05 12:52 ` ubizjak at gmail dot com 2021-03-05 12:55 ` rguenther at suse dot de 2021-03-05 13:06 ` rguenth at gcc dot gnu.org 2021-03-05 13:08 ` ubizjak at gmail dot com 2021-03-05 14:35 ` rguenth at gcc dot gnu.org 2021-03-08 10:41 ` rguenth at gcc dot gnu.org 2021-03-08 13:20 ` rguenth at gcc dot gnu.org 2021-03-08 15:46 ` amonakov at gcc dot gnu.org 2021-04-27 11:40 ` [Bug tree-optimization/98856] [11/12 " jakub at gcc dot gnu.org 2021-05-13 10:17 ` cvs-commit at gcc dot gnu.org 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2022-01-21 13:20 ` rguenth at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2023-04-17 21:43 ` [Bug tree-optimization/98856] [11/12/13/14 " lukebenes at hotmail dot com 2023-04-18 9:07 ` rguenth at gcc dot gnu.org 2023-05-29 10:04 ` jakub 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-98856-4-rchDEQiJsN@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).