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 rtl-optimization/93974] [10 Regression] ICE in decompose_normal_address, at rtlanal.c:6403 on powerpc64le-linux-gnu since r10-6762
Date: Wed, 15 Apr 2020 22:35:10 +0000	[thread overview]
Message-ID: <bug-93974-4-sAabGnlT7z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93974-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #22 from Peter Bergner <bergner at gcc dot gnu.org> ---
To be more specific, I have implemented the hook cannot_substitute_mem_equiv_p
for rs6000 that rejects these and: altivec addresses.  The nice thing about the
patch is that it only affects rs6000, whereas a lra-constraints.c or rtlanal.c
change could affect everyone.

I have confirmed that the test case in Comment #1 compiles and we get the same
asm generated as a compiler built with the revision before my patch that caused
the ICE.  I also confirmed that test case pr93658.c which used to go into an
infinite loop in LRA before my previous patch still compiles fine.

I'm running the testsuite now to see whether there are any regressions.

Whether this is the best long term fix is unknown right now (it could be), but
it might be the best thing for GCC 10 with the release so close.  I'd rather
not revert the fix for PR93658 just to hide this bug again.

  parent reply	other threads:[~2020-04-15 22:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-93974-4@http.gcc.gnu.org/bugzilla/>
2020-04-01  8:09 ` jakub at gcc dot gnu.org
2020-04-01  8:10 ` jakub at gcc dot gnu.org
2020-04-01 15:58 ` bergner at gcc dot gnu.org
2020-04-01 16:02 ` jakub at gcc dot gnu.org
2020-04-01 16:09 ` bergner at gcc dot gnu.org
2020-04-15  9:58 ` jakub at gcc dot gnu.org
2020-04-15 20:05 ` bergner at gcc dot gnu.org
2020-04-15 22:35 ` bergner at gcc dot gnu.org [this message]
2020-04-15 23:24 ` segher at gcc dot gnu.org
2020-04-17  4:27 ` cvs-commit at gcc dot gnu.org
2020-04-17  4:28 ` 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-93974-4-sAabGnlT7z@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).