public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104681] New: [9/10/11/12 Regression] ppc64le -mabi=ieeelongdouble ICE since r9-6460 Date: Thu, 24 Feb 2022 20:29:57 +0000 [thread overview] Message-ID: <bug-104681-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104681 Bug ID: 104681 Summary: [9/10/11/12 Regression] ppc64le -mabi=ieeelongdouble ICE since r9-6460 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org Target Milestone: --- The following testcase ICEs on powerpc64le-linux with -O2 -mabi=ieeelongdouble since r9-6460-gb496651b7d281bd1bf22688f4de0cbb78c1bf8e5: struct A { A(bool) : a(__builtin_nansl ("")), b(0) {} long double a; long b; }; struct B { void foo() { void bar(); c = bar; } A c; }; struct C { void baz(); B d; }; void C::baz() { d.foo(); } cc7NbdyL.C: In member function ‘void C::baz()’: cc7NbdyL.C:17:26: error: unrecognizable insn: 17 | void C::baz() { d.foo(); } | ^ (insn 6 3 7 2 (set (mem:TF (reg/f:DI 121 [ this ]) [3 MEM[(struct A *)this_1(D)]+0 S16 A8]) (const_double:TF +SNaN [+SNaN])) "cc7NbdyL.C":9:7 -1 (nil)) during RTL pass: vregs cc7NbdyL.C:17:26: internal compiler error: in extract_insn, at recog.c:2310 I think the reason for it is the movmisalign<mode> expander which is just: (define_expand "movmisalign<mode>" [(set (match_operand:VEC_N 0 "nonimmediate_operand") (match_operand:VEC_N 1 "any_operand"))] "VECTOR_MEM_VSX_P (<MODE>mode) && TARGET_ALLOW_MOVMISALIGN" "") and so doesn't what normal "mov<mode>" expanders do - rs6000_emit_move - which e.g. for the MEM destinations and CONST_DOUBLE sources forces the sources into reg.
next reply other threads:[~2022-02-24 20:29 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-24 20:29 jakub at gcc dot gnu.org [this message] 2022-02-24 20:30 ` [Bug target/104681] " jakub at gcc dot gnu.org 2022-02-25 11:55 ` jakub at gcc dot gnu.org 2022-02-25 15:40 ` segher at gcc dot gnu.org 2022-02-25 15:43 ` jakub at gcc dot gnu.org 2022-02-25 17:05 ` segher at gcc dot gnu.org 2022-02-25 18:02 ` cvs-commit at gcc dot gnu.org 2022-02-25 18:03 ` [Bug target/104681] [9/10/11 " jakub at gcc dot gnu.org 2022-03-29 5:53 ` cvs-commit at gcc dot gnu.org 2022-03-30 8:15 ` [Bug target/104681] [9/10 " jakub at gcc dot gnu.org 2022-05-10 8:24 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:25 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:36 ` 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-104681-4@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).