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/108807] [11/12 regression] gcc.target/powerpc/vsx-builtin-10d.c fails after r11-6857-gb29225597584b6 on power 9 BE Date: Mon, 17 Apr 2023 09:08:05 +0000 [thread overview] Message-ID: <bug-108807-4-rmWczic4I2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108807-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108807 --- Comment #9 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:043cc707f449076ea704a12fff60e32f5861dfcb commit r11-10627-g043cc707f449076ea704a12fff60e32f5861dfcb Author: Kewen Lin <linkw@linux.ibm.com> Date: Mon Apr 3 21:47:54 2023 -0500 rs6000: Fix vector_set_var_p9 by considering BE [PR108807] As PR108807 exposes, the current handling in function rs6000_expand_vector_set_var_p9 doesn't take care of big endianness. Currently the function is to rotate the target vector by moving element to-be-set to element 0, set element 0 with the given val, then rotate back. To get the permutation control vector for the rotation, it makes use of lvsr and lvsl, but the element ordering is different for BE and LE (like element 0 is the most significant one on BE while the least significant one on LE), this patch is to add consideration for BE and make sure permutation control vectors for rotations are expected. As tested, it helped to fix the below failures: FAIL: gcc.target/powerpc/pr79251-run.p9.c execution test FAIL: gcc.target/powerpc/pr89765-mc.c execution test FAIL: gcc.target/powerpc/vsx-builtin-10d.c execution test FAIL: gcc.target/powerpc/vsx-builtin-11d.c execution test FAIL: gcc.target/powerpc/vsx-builtin-14d.c execution test FAIL: gcc.target/powerpc/vsx-builtin-16d.c execution test FAIL: gcc.target/powerpc/vsx-builtin-18d.c execution test FAIL: gcc.target/powerpc/vsx-builtin-9d.c execution test PR target/108807 gcc/ChangeLog: * config/rs6000/rs6000.c (rs6000_expand_vector_set_var_p9): Fix gen function for permutation control vector by considering big endianness. (cherry picked from commit d634e6088f139ee700d79ec73b1ad6436096a6ff)
next prev parent reply other threads:[~2023-04-17 9:08 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-15 19:16 [Bug target/108807] New: [11 regression] gcc.target/powerpc/vsx-builtin-10d.c fails after b29225597584b697762585e0b707b7cb4b427650 " seurer at gcc dot gnu.org 2023-02-16 7:41 ` [Bug target/108807] " linkw at gcc dot gnu.org 2023-02-17 4:09 ` [Bug target/108807] [11/12/13 regression] gcc.target/powerpc/vsx-builtin-10d.c fails after r11-6857-gb29225597584b6 " linkw at gcc dot gnu.org 2023-02-17 5:26 ` linkw at gcc dot gnu.org 2023-03-15 10:02 ` rguenth at gcc dot gnu.org 2023-04-04 5:13 ` cvs-commit at gcc dot gnu.org 2023-04-14 15:33 ` law at gcc dot gnu.org 2023-04-15 9:55 ` [Bug target/108807] [11/12 " linkw at gcc dot gnu.org 2023-04-15 13:19 ` law 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:10 ` 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-108807-4-rmWczic4I2@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).