public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia 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 Date: Fri, 13 Jan 2023 19:00:41 +0000 [thread overview] Message-ID: <bug-108396-4-YPvUm8cUu2@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 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |rejects-valid Summary|PPCLE: vec_vsubcuq missing |[12/13 Regression] PPCLE: | |vec_vsubcuq missing Last reconfirmed| |2023-01-13 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Target Milestone|--- |12.3 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- This looks like a regression introduced by r12-3169-ge2693a72701fe5 . rs6000-overload.def:[VEC_VSUBCUQ, vec_vsubcuqP, __builtin_vec_vsubcuq] There looks like a typo of including a P in the overload name for some reason ...
next prev parent reply other threads:[~2023-01-13 19:00 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-13 16:24 [Bug target/108396] New: " jens.seifert at de dot ibm.com 2023-01-13 19:00 ` pinskia at gcc dot gnu.org [this message] 2023-01-16 7:38 ` [Bug target/108396] [12/13 Regression] " 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 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-YPvUm8cUu2@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).