public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/104868] powerpc: Compiling libgfortran with -flto failing with GCC 12 Date: Thu, 10 Mar 2022 18:23:56 +0000 [thread overview] Message-ID: <bug-104868-4-lWvqJ6vhCk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104868-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104868 Segher Boessenkool <segher at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |segher at gcc dot gnu.org --- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> --- operands[1] is "b", but is given GPR 0 here. The instruction pattern should handle that case. Luckily it can just use "r" here. === diff --git a/gcc/config/rs6000/vsx.md b/gcc/config/rs6000/vsx.md index b53de1038725..a84ae5df7c0c 100644 --- a/gcc/config/rs6000/vsx.md +++ b/gcc/config/rs6000/vsx.md @@ -4576,7 +4576,7 @@ (define_expand "vsx_splat_<mode>" (define_insn "vsx_splat_<mode>_reg" [(set (match_operand:VSX_D 0 "vsx_register_operand" "=wa,we") (vec_duplicate:VSX_D - (match_operand:<VS_scalar> 1 "gpc_reg_operand" "wa,b")))] + (match_operand:<VS_scalar> 1 "gpc_reg_operand" "wa,r")))] "VECTOR_MEM_VSX_P (<MODE>mode)" "@ xxpermdi %x0,%x1,%x1,0 === Try with that?
next prev parent reply other threads:[~2022-03-10 18:23 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-10 18:11 [Bug lto/104868] New: " msc at linux dot ibm.com 2022-03-10 18:23 ` segher at gcc dot gnu.org [this message] 2022-03-10 18:34 ` [Bug lto/104868] " segher at gcc dot gnu.org 2022-03-10 19:13 ` segher at gcc dot gnu.org 2022-03-10 19:53 ` meissner at gcc dot gnu.org 2022-03-10 21:48 ` [Bug target/104868] [12 Regression] " pinskia at gcc dot gnu.org 2022-03-10 22:50 ` segher at gcc dot gnu.org 2022-03-11 14:44 ` msc at linux dot ibm.com 2022-03-11 16:11 ` meissner at gcc dot gnu.org 2022-03-11 16:12 ` meissner at gcc dot gnu.org 2022-03-11 16:44 ` msc at linux dot ibm.com 2022-03-12 0:47 ` cvs-commit at gcc dot gnu.org 2022-03-28 13:18 ` jakub 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-104868-4-lWvqJ6vhCk@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).