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/108699] gcc.c-torture/execute/builtin-bitops-1.c fails on power 9 BE Date: Mon, 17 Apr 2023 09:08:09 +0000 [thread overview] Message-ID: <bug-108699-4-O3UhuQMmZH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108699-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108699 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>: https://gcc.gnu.org/g:6872f055d7d4fd36b804bdd9b5a8a128b01aacbc commit r11-10628-g6872f055d7d4fd36b804bdd9b5a8a128b01aacbc Author: Kewen Lin <linkw@linux.ibm.com> Date: Sun Apr 16 22:31:01 2023 -0500 rs6000: Fix vector parity support [PR108699] The failures on the original failed case builtin-bitops-1.c and the associated test case pr108699.c here show that the current support of parity vector mode is wrong on Power. The hardware insns vprtyb[wdq] which operate on the least significant bit of each byte per element, they doesn't match what RTL opcode parity needs, but the current implementation expands it with them wrongly. This patch is to fix the handling with one more insn vpopcntb. PR target/108699 gcc/ChangeLog: * config/rs6000/altivec.md (*p9v_parity<mode>2): Rename to ... (rs6000_vprtyb<mode>2): ... this. * config/rs6000/rs6000-builtin.def (VPRTYBD): Replace parityv2di2 with rs6000_vprtybv2di2. (VPRTYBW): Replace parityv4si2 with rs6000_vprtybv4si2. (VPRTYBQ): Replace parityv1ti2 with rs6000_vprtybv1ti2. * config/rs6000/vector.md (parity<mode>2 with VEC_IP): Expand with popcountv16qi2 and the corresponding rs6000_vprtyb<mode>2. gcc/testsuite/ChangeLog: * gcc.target/powerpc/p9-vparity.c: Add scan-assembler-not for vpopcntb to distinguish parity byte from parity. * gcc.target/powerpc/pr108699.c: New test. (cherry picked from commit cdd2d6643f7fef40e335a7027edfea7276cde608)
next prev parent reply other threads:[~2023-04-17 9:08 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-07 15:01 [Bug target/108699] New: " seurer at gcc dot gnu.org 2023-02-14 12:12 ` [Bug target/108699] " linkw at gcc dot gnu.org 2023-02-14 17:39 ` segher at gcc dot gnu.org 2023-02-15 2:34 ` linkw at gcc dot gnu.org 2023-04-04 5:13 ` cvs-commit at gcc dot gnu.org 2023-04-17 9:06 ` cvs-commit at gcc dot gnu.org 2023-04-17 9:08 ` cvs-commit at gcc dot gnu.org [this message] 2023-04-17 9:09 ` cvs-commit at gcc dot gnu.org 2023-06-02 4:15 ` bergner at gcc dot gnu.org 2023-06-02 4:42 ` linkw 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-108699-4-O3UhuQMmZH@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).