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, 22 Jun 2021 02:05:38 +0000 [thread overview]
Message-ID: <bug-100866-4-OK9wrBJjjO@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
--- Comment #13 from luoxhu at gcc dot gnu.org ---
It is not visible in combine due to the constant data is in *.LC0 and
UNSPEC_VPERM. Will shelf this and switch to other high priority issues.
pr100866.c.277r.combine:
(note 4 0 20 2 [bb 2] NOTE_INSN_BASIC_BLOCK)
(insn 20 4 2 2 (set (reg:V8HI 126)
(reg:V8HI 66 %v2 [ a ])) "pr100866.c":18:1 1132 {vsx_movv8hi_64bit}
(expr_list:REG_DEAD (reg:V8HI 66 %v2 [ a ])
(nil)))
(note 2 20 3 2 NOTE_INSN_DELETED)
(note 3 2 6 2 NOTE_INSN_FUNCTION_BEG)
(insn 6 3 18 2 (set (reg/f:DI 122)
(unspec:DI [
(symbol_ref/u:DI ("*.LC0") [flags 0x82])
(reg:DI 2 %r2)
] UNSPEC_TOCREL)) "pr100866.c":19:13 719 {*tocrefdi}
(expr_list:REG_EQUAL (symbol_ref/u:DI ("*.LC0") [flags 0x82])
(nil)))
(insn 18 6 9 2 (set (reg:V16QI 123)
(mem/u/c:V16QI (and:DI (reg/f:DI 122)
(const_int -16 [0xfffffffffffffff0])) [0 S16 A128]))
"pr100866.c":19:13 1131 {vsx_movv16qi_64bit}
(expr_list:REG_DEAD (reg/f:DI 122)
(nil)))
(insn 9 18 10 2 (set (reg:V16QI 124)
(not:V16QI (reg:V16QI 123))) "pr100866.c":19:13 508 {one_cmplv16qi2}
(expr_list:REG_DEAD (reg:V16QI 123)
(nil)))
(note 10 9 15 2 NOTE_INSN_DELETED)
(insn 15 10 16 2 (set (reg/i:V8HI 66 %v2)
(unspec:V8HI [
(reg:V8HI 126) repeated x2
(reg:V16QI 124)
] UNSPEC_VPERM)) "pr100866.c":20:1 1830 {altivec_vperm_v8hi_direct}
(expr_list:REG_DEAD (reg:V16QI 124)
(expr_list:REG_DEAD (reg:V8HI 126)
(nil))))
(insn 16 15 0 2 (use (reg/i:V8HI 66 %v2)) "pr100866.c":20:1 -1
(nil))
;; Combiner totals: 12 attempts, 12 substitutions (2 requiring new space),
next prev parent reply other threads:[~2021-06-22 2:05 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
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 [this message]
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-OK9wrBJjjO@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: link
Be 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).