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/108396] [12/13 Regression] PPCLE: vec_vsubcuq missing since r12-5752-gd08236359eb229 Date: Mon, 13 Feb 2023 02:03:58 +0000 [thread overview] Message-ID: <bug-108396-4-vSVB4OoCkz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108396-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108396 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>: https://gcc.gnu.org/g:cb6861acc4074fd2c30a96b52d68c2cd33b9e94d commit r12-9170-gcb6861acc4074fd2c30a96b52d68c2cd33b9e94d Author: Kewen Lin <linkw@linux.ibm.com> Date: Wed Jan 18 02:34:25 2023 -0600 rs6000: Fix typo on vec_vsubcuq in rs6000-overload.def [PR108396] As Andrew pointed out in PR108396, there is one typo in rs6000-overload.def on built-in function vec_vsubcuq: [VEC_VSUBCUQ, vec_vsubcuqP, __builtin_vec_vsubcuq] "vec_vsubcuqP" should be "vec_vsubcuq", this typo caused us to define vec_vsubcuqP in rs6000-vecdefines.h instead of vec_vsubcuq, so that compiler is not able to realize the built-in function name vec_vsubcuq any more. Co-authored-By: Andrew Pinski <apinski@marvell.com> PR target/108396 gcc/ChangeLog: * config/rs6000/rs6000-overload.def (VEC_VSUBCUQ): Fix typo vec_vsubcuqP with vec_vsubcuq. gcc/testsuite/ChangeLog: * gcc.target/powerpc/pr108396.c: New test. (cherry picked from commit aaf29ae6cdbaad58b709a77784375d15138174b3)
next prev parent reply other threads:[~2023-02-13 2:03 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-13 16:24 [Bug target/108396] New: PPCLE: vec_vsubcuq missing jens.seifert at de dot ibm.com 2023-01-13 19:00 ` [Bug target/108396] [12/13 Regression] " pinskia at gcc dot gnu.org 2023-01-16 7:38 ` rguenth at gcc dot gnu.org 2023-01-16 9:58 ` [Bug target/108396] [12/13 Regression] PPCLE: vec_vsubcuq missing since r12-5752-gd08236359eb229 linkw at gcc dot gnu.org 2023-01-16 16:35 ` segher at gcc dot gnu.org 2023-01-17 3:03 ` linkw at gcc dot gnu.org 2023-01-17 11:56 ` segher at gcc dot gnu.org 2023-01-18 8:35 ` cvs-commit at gcc dot gnu.org 2023-02-13 2:03 ` cvs-commit at gcc dot gnu.org [this message] 2023-02-13 2:21 ` linkw at gcc dot gnu.org 2023-10-05 18:01 ` carll at gcc dot gnu.org 2023-10-12 6: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-108396-4-vSVB4OoCkz@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).