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/95082] [11/12] LE implementations of vec_cnttz_lsbb and vec_cntlz_lsbb are wrong Date: Thu, 03 Feb 2022 17:17:27 +0000 [thread overview] Message-ID: <bug-95082-4-NWHrpy6beb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95082-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95082 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by William Schmidt <wschmidt@gcc.gnu.org>: https://gcc.gnu.org/g:3f30f2d1dbb3228b8468b26239fe60c2974ce2ac commit r12-7029-g3f30f2d1dbb3228b8468b26239fe60c2974ce2ac Author: Bill Schmidt <wschmidt@linux.ibm.com> Date: Wed Feb 2 21:24:22 2022 -0600 rs6000: Fix LE code gen for vec_cnt[lt]z_lsbb [PR95082] These built-ins were misimplemented as always having big-endian semantics. 2022-01-18 Bill Schmidt <wschmidt@linux.ibm.com> gcc/ PR target/95082 * config/rs6000/rs6000-builtin.cc (rs6000_expand_builtin): Handle endianness for vclzlsbb and vctzlsbb. * config/rs6000/rs6000-builtins.def (VCLZLSBB_V16QI): Change default pattern and indicate a different pattern will be used for big endian. (VCLZLSBB_V4SI): Likewise. (VCLZLSBB_V8HI): Likewise. (VCTZLSBB_V16QI): Likewise. (VCTZLSBB_V4SI): Likewise. (VCTZLSBB_V8HI): Likewise. gcc/testsuite/ PR target/95082 * gcc.target/powerpc/vsu/vec-cntlz-lsbb-0.c: Restrict to -mbig. * gcc.target/powerpc/vsu/vec-cntlz-lsbb-1.c: Likewise. * gcc.target/powerpc/vsu/vec-cntlz-lsbb-3.c: New. * gcc.target/powerpc/vsu/vec-cntlz-lsbb-4.c: New. * gcc.target/powerpc/vsu/vec-cnttz-lsbb-0.c: Restrict to -mbig. * gcc.target/powerpc/vsu/vec-cnttz-lsbb-1.c: Likewise. * gcc.target/powerpc/vsu/vec-cnttz-lsbb-3.c: New. * gcc.target/powerpc/vsu/vec-cnttz-lsbb-4.c: New.
next prev parent reply other threads:[~2022-02-03 17:17 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-12 13:34 [Bug target/95082] New: " wschmidt at gcc dot gnu.org 2020-05-12 13:34 ` [Bug target/95082] " wschmidt at gcc dot gnu.org 2020-05-15 0:53 ` pc at us dot ibm.com 2020-05-15 10:50 ` segher at gcc dot gnu.org 2020-05-15 10:51 ` segher at gcc dot gnu.org 2021-04-27 11:38 ` jakub at gcc dot gnu.org 2021-07-28 7:04 ` rguenth at gcc dot gnu.org 2022-01-18 15:15 ` wschmidt at gcc dot gnu.org 2022-02-03 17:17 ` cvs-commit at gcc dot gnu.org [this message] 2022-02-11 13:59 ` [Bug target/95082] [11] " wschmidt at gcc dot gnu.org 2022-02-11 15:15 ` segher at gcc dot gnu.org 2022-02-23 20:25 ` [Bug target/95082] " wschmidt 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-95082-4-NWHrpy6beb@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).