public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102868] Missed optimization with __builtin_shuffle and zero vector on ppc
Date: Fri, 29 Oct 2021 02:28:56 +0000 [thread overview]
Message-ID: <bug-102868-4-gYV048QSfu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102868-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102868
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Xiong Hu Luo <luoxhu@gcc.gnu.org>:
https://gcc.gnu.org/g:146b83e14a0a76a9ce8a4cb79997a078f437f779
commit r12-4781-g146b83e14a0a76a9ce8a4cb79997a078f437f779
Author: Xionghu Luo <luoxhu@linux.ibm.com>
Date: Thu Oct 28 21:28:43 2021 -0500
rs6000: Optimize __builtin_shuffle when it's used to zero the upper bits
[PR102868]
If the second operand of __builtin_shuffle is const vector 0, and with
specific mask, it can be optimized to vspltisw+xxpermdi instead of lxv.
gcc/ChangeLog:
PR target/102868
* config/rs6000/rs6000.c (altivec_expand_vec_perm_const): Add
patterns match and emit for VSX xxpermdi.
gcc/testsuite/ChangeLog:
PR target/102868
* gcc.target/powerpc/pr102868.c: New test.
next prev parent reply other threads:[~2021-10-29 2:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 6:08 [Bug target/102868] New: " luoxhu at gcc dot gnu.org
2021-10-25 2:52 ` [Bug target/102868] " luoxhu at gcc dot gnu.org
2021-10-29 2:28 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-29 2:31 ` luoxhu 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-102868-4-gYV048QSfu@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).