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/98959] ICE in extract_constrain_insn, at recog.c:2670
Date: Thu, 04 Feb 2021 17:01:23 +0000	[thread overview]
Message-ID: <bug-98959-4-gyWQ1v01BF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98959-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98959

--- Comment #8 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #2)
> I do not set any default CPU:

The default cpu on ppc64le is (should be!) POWER8.

That said, I cannot recreate the issue with a cross build using current trunk. 
I will say that the change you identified did cause some fallout that was fixed
with a later change (below) that looks related to the bad insn you are seeing. 
Maybe this is a bisec issue?  Does adding the later fix from the following
"fix" the ICE?

commit dd75498db79675a1a0b73c25e5f110969ee72d9d
Author:     Peter Bergner <bergner@linux.ibm.com>
AuthorDate: Thu Apr 16 23:26:41 2020 -0500
Commit:     Peter Bergner <bergner@linux.ibm.com>
CommitDate: Thu Apr 16 23:26:41 2020 -0500

    rs6000: Fix ICE in decompose_normal_address. [PR93974]

    Fix an ICE in decompose_normal_address(), which cannot handle Altivec AND:
    addresses, by disallowing them via implementing the target hook
    rs6000_cannot_substitute_mem_equiv_p.

    gcc/
            PR rtl-optimization/93974
            * config/rs6000/rs6000.c (TARGET_CANNOT_SUBSTITUTE_MEM_EQUIV_P):
Define.
            (rs6000_cannot_substitute_mem_equiv_p): New function.

    gcc/testsuite/
            PR rtl-optimization/93974
            * g++.dg/pr93974.C: New test.

If that fixes it, are you really seeing the same ICE on current trunk?

  parent reply	other threads:[~2021-02-04 17:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03 18:52 [Bug target/98959] New: " marxin at gcc dot gnu.org
2021-02-03 18:52 ` [Bug target/98959] " marxin at gcc dot gnu.org
2021-02-04 11:44 ` jakub at gcc dot gnu.org
2021-02-04 12:19 ` marxin at gcc dot gnu.org
2021-02-04 13:20 ` marxin at gcc dot gnu.org
2021-02-04 13:20 ` marxin at gcc dot gnu.org
2021-02-04 13:23 ` marxin at gcc dot gnu.org
2021-02-04 13:24 ` marxin at gcc dot gnu.org
2021-02-04 16:33 ` bergner at gcc dot gnu.org
2021-02-04 17:01 ` bergner at gcc dot gnu.org [this message]
2021-02-04 17:08 ` marxin at gcc dot gnu.org
2021-02-04 18:18 ` jakub at gcc dot gnu.org
2021-02-04 19:29 ` bergner at gcc dot gnu.org
2021-02-04 19:37 ` bergner at gcc dot gnu.org
2021-02-05  0:13 ` bergner at gcc dot gnu.org
2021-02-07 22:06 ` wschmidt at gcc dot gnu.org
2021-02-11 22:28 ` bergner at gcc dot gnu.org
2021-02-11 23:56 ` bergner at gcc dot gnu.org
2021-02-11 23:59 ` bergner at gcc dot gnu.org
2021-02-12 20:51 ` bergner at gcc dot gnu.org
2021-03-08 18:24 ` cvs-commit at gcc dot gnu.org
2021-03-10 19:09 ` bergner at gcc dot gnu.org
2021-03-10 21:31 ` segher at gcc dot gnu.org
2021-03-10 23:48 ` cvs-commit at gcc dot gnu.org
2021-03-11  0:03 ` 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-98959-4-gyWQ1v01BF@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: link
Be 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).