public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/101846] Improve __builtin_shufflevector emitted code Date: Tue, 10 Aug 2021 14:30:52 +0000 [thread overview] Message-ID: <bug-101846-4-FUTw9eRSZL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101846-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101846 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-08-10 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. I've pondered (for elsewhere) about how to represent "paradoxical subregs" on GIMPLE. We expand from v32hi foo (v16hi x) { vector(32) short int _1; v32hi _3; ;; basic block 2, loop depth 0 ;; pred: ENTRY _1 = {x_2(D), { 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }}; _3 = VEC_PERM_EXPR <_1, { 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }, { 0, 32, 1, 33, 2, 34, 3, 35, 4, 36, 5, 37, 6, 38, 7, 39, 8, 40, 9, 41, 10, 42, 11, 43, 12, 44, 13, 45, 14, 46, 15, 47 }>; return _3; and v16hi bar (v32hi x) { vector(32) short int _1; v16hi _3; ;; basic block 2, loop depth 0 ;; pred: ENTRY _1 = VEC_PERM_EXPR <x_2(D), x_2(D), { 0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31 }>; _3 = BIT_FIELD_REF <_1, 256, 0>; return _3; I think bar() is reasonable from the GIMPLE side, it would be a 1:1 canonicalization choice to move the BIT_FIELD_REF across the permute (and something only "profitable" for single operand permutes). For foo() I thought of doing _1 = BIT_INSERT_EXPR <tem_3(D), x_2(D), 0>; with tem_3(D) being uninitialized as to represent a paradoxical subreg. I've tested and disregarded the idea of simply doing VIEW_CONVERT_EXPRs here but I'm considering it for the case where we need the lowpart of a vector and the the highpart doesn't matter (aka %xmm0 vs %ymm0) since the current representation of doing a BIT_FIELD_REF doesn't seem to optimize well (that was in the context of AVX512 mask registers though). I suppose the testcases can be optimized on the RTL level as well.
next prev parent reply other threads:[~2021-08-10 14:30 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-10 13:14 [Bug target/101846] New: " jakub at gcc dot gnu.org 2021-08-10 14:30 ` rguenth at gcc dot gnu.org [this message] 2021-08-11 3:35 ` [Bug target/101846] " crazylht at gmail dot com 2021-08-12 1:53 ` crazylht at gmail dot com 2021-08-12 1:55 ` crazylht at gmail dot com 2021-08-12 6:03 ` cvs-commit at gcc dot gnu.org 2021-08-16 7:30 ` cvs-commit at gcc dot gnu.org 2021-12-15 1:50 ` pinskia at gcc dot gnu.org 2021-12-15 1:52 ` pinskia at gcc dot gnu.org 2021-12-15 3:25 ` crazylht at gmail dot com 2021-12-15 11:26 ` 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-101846-4-FUTw9eRSZL@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).