public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99041] combine creates invalid address which ICEs in decompose_normal_address Date: Wed, 10 Feb 2021 20:51:10 +0000 [thread overview] Message-ID: <bug-99041-4-TgCxHYaJ0O@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99041-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99041 Peter Bergner <bergner at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #6 from Peter Bergner <bergner at gcc dot gnu.org> --- (In reply to Peter Bergner from comment #3) > Ahh, ok. I can make that more robust. Thanks for the pointer! The mma_assemble_pair/mma_assemble_acc patterns both generate lxv or lxvp instructions, which both use a DQ offset and we already have function to test for that. The following change fixes the ICE, so I'll give it a spin on regtesting. diff --git a/gcc/config/rs6000/predicates.md b/gcc/config/rs6000/predicates.md index 76328ecff3d..bd26c62b3a4 100644 --- a/gcc/config/rs6000/predicates.md +++ b/gcc/config/rs6000/predicates.md @@ -1156,7 +1156,9 @@ ;; Return 1 if this operand is valid for a MMA assemble accumulator insn. (define_special_predicate "mma_assemble_input_operand" (match_test "(mode == V16QImode - && (vsx_register_operand (op, mode) || MEM_P (op)))")) + && (vsx_register_operand (op, mode) + || (MEM_P (op) + && quad_address_p (XEXP (op, 0), mode, false))))")) ;; Return 1 if this operand is valid for an MMA disassemble insn. (define_predicate "mma_disassemble_output_operand"
next prev parent reply other threads:[~2021-02-10 20:51 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-09 18:51 [Bug rtl-optimization/99041] New: " bergner at gcc dot gnu.org 2021-02-09 18:52 ` [Bug rtl-optimization/99041] " bergner at gcc dot gnu.org 2021-02-09 19:02 ` jakub at gcc dot gnu.org 2021-02-09 19:13 ` bergner at gcc dot gnu.org 2021-02-09 20:52 ` segher at gcc dot gnu.org 2021-02-09 20:55 ` segher at gcc dot gnu.org 2021-02-10 20:51 ` bergner at gcc dot gnu.org [this message] 2021-02-10 21:27 ` [Bug target/99041] " segher at gcc dot gnu.org 2021-02-11 20:16 ` cvs-commit at gcc dot gnu.org 2021-02-11 20:24 ` bergner at gcc dot gnu.org 2021-02-11 21:07 ` bergner at gcc dot gnu.org 2021-03-10 23:48 ` cvs-commit at gcc dot gnu.org 2021-03-10 23:50 ` bergner 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-99041-4-TgCxHYaJ0O@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).