public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "luoxhu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100866] PPC: Inefficient code for vec_revb(vector unsigned short) < P9 Date: Tue, 15 Jun 2021 09:22:59 +0000 [thread overview] Message-ID: <bug-100866-4-zaovrP7hSK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100866-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100866 luoxhu at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |luoxhu at gcc dot gnu.org --- Comment #2 from luoxhu at gcc dot gnu.org --- But it only works for V8HImode, no better code generation for other modes like V4SI/V2DI/V1TI to do byte swap with only two instructions vspltish+vrlh? unsigned int swap1[16] = {15,14,13,12,11,10,9,8,7,6,5,4,3,2,1,0}; unsigned int swap2[16] = {7,6,5,4,3,2,1,0,15,14,13,12,11,10,9,8}; unsigned int swap4[16] = {3,2,1,0,7,6,5,4,11,10,9,8,15,14,13,12}; unsigned int swap8[16] = {1,0,3,2,5,4,7,6,9,8,11,10,13,12,15,14}; For example V4SI, need swap short first, then swap word, it seems not so straight forward than vperm?
next prev parent reply other threads:[~2021-06-15 9:22 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-02 7:14 [Bug target/100866] New: " jens.seifert at de dot ibm.com 2021-06-02 15:03 ` [Bug target/100866] " segher at gcc dot gnu.org 2021-06-15 9:22 ` luoxhu at gcc dot gnu.org [this message] 2021-06-15 9:56 ` luoxhu at gcc dot gnu.org 2021-06-15 13:50 ` segher at gcc dot gnu.org 2021-06-16 5:53 ` luoxhu at gcc dot gnu.org 2021-06-18 1:37 ` luoxhu at gcc dot gnu.org 2021-06-18 8:32 ` jens.seifert at de dot ibm.com 2021-06-21 2:29 ` luoxhu at gcc dot gnu.org 2021-06-21 4:20 ` jens.seifert at de dot ibm.com 2021-06-21 12:42 ` wschmidt at gcc dot gnu.org 2021-06-21 12:46 ` wschmidt at gcc dot gnu.org 2021-06-21 19:27 ` segher at gcc dot gnu.org 2021-06-22 2:05 ` luoxhu at gcc dot gnu.org 2021-06-23 20:06 ` segher at gcc dot gnu.org 2022-11-02 8:42 ` cvs-commit at gcc dot gnu.org 2022-12-01 2:07 ` cvs-commit at gcc dot gnu.org 2022-12-14 5:52 ` guihaoc 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-100866-4-zaovrP7hSK@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).