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/94613] S/390, powerpc: Wrong code generated for vec_sel builtin
Date: Thu, 28 Oct 2021 03:18:20 +0000 [thread overview]
Message-ID: <bug-94613-4-n3Yp6wpURb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94613-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94613
--- Comment #16 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:5f9ef1339e9d0d709af6a70b60e584bf7decd761
commit r12-4758-g5f9ef1339e9d0d709af6a70b60e584bf7decd761
Author: Xionghu Luo <luoxhu@linux.ibm.com>
Date: Wed Oct 27 21:22:39 2021 -0500
rs6000: Fold xxsel to vsel since they have same semantics
Fold xxsel to vsel like xxperm/vperm to avoid duplicate code.
gcc/ChangeLog:
2021-10-28 Xionghu Luo <luoxhu@linux.ibm.com>
PR target/94613
* config/rs6000/altivec.md: Add vsx register constraints.
* config/rs6000/vsx.md (vsx_xxsel<mode>): Delete.
(vsx_xxsel<mode>2): Likewise.
(vsx_xxsel<mode>3): Likewise.
(vsx_xxsel<mode>4): Likewise.
gcc/testsuite/ChangeLog:
2021-10-28 Xionghu Luo <luoxhu@linux.ibm.com>
* gcc.target/powerpc/builtins-1.c: Adjust.
next prev parent reply other threads:[~2021-10-28 3:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 7:01 [Bug rtl-optimization/94613] New: combine: Wrong code due to splitting a simplified IF_THEN_ELSE krebbel at gcc dot gnu.org
2020-04-16 7:02 ` [Bug rtl-optimization/94613] " krebbel at gcc dot gnu.org
2020-04-16 7:05 ` krebbel at gcc dot gnu.org
2020-04-16 7:05 ` krebbel at gcc dot gnu.org
2020-04-16 7:09 ` krebbel at gcc dot gnu.org
2020-04-16 7:10 ` rguenth at gcc dot gnu.org
2020-04-16 7:15 ` rguenth at gcc dot gnu.org
2020-04-16 7:37 ` krebbel at gcc dot gnu.org
2020-04-16 8:21 ` [Bug target/94613] Wrong code generated for vec_sel builtin krebbel at gcc dot gnu.org
2020-04-16 8:28 ` [Bug target/94613] S/390: " krebbel at gcc dot gnu.org
2020-04-16 21:18 ` segher at gcc dot gnu.org
2020-04-20 17:39 ` [Bug target/94613] S/390, powerpc: " cvs-commit at gcc dot gnu.org
2020-05-04 8:39 ` cvs-commit at gcc dot gnu.org
2020-05-04 8:43 ` cvs-commit at gcc dot gnu.org
2020-05-07 11:56 ` jakub at gcc dot gnu.org
2020-07-23 6:52 ` rguenth at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-05-04 12:32 ` rguenth at gcc dot gnu.org
2021-05-27 0:57 ` luoxhu at gcc dot gnu.org
2021-10-28 3:18 ` cvs-commit at gcc dot gnu.org
2021-10-28 3:18 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-28 6:04 ` 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-94613-4-n3Yp6wpURb@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).