public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61411] [NEON] ICE in reload_cse_simplify_operands, at postreload.c:411
Date: Thu, 05 Jun 2014 13:54:00 -0000	[thread overview]
Message-ID: <bug-61411-4-nrYs83BIT2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61411-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to bin.cheng from comment #1)
> The patch can fix the issue, but problem is why GCC/lra generated
> register-indexing ([reg+reg]) addressing mode for V8HImode in the first
> place.  Since without this patch, the address expression is illegal and
> shouldn't be generated.  I didn't look into LRA's code and am not very sure
> whether this patch is covering the problem.

LRA does a lot of RTL transformations during its work.  One transformation can
be rematerialization -- changing one reg (usually a spilled pseudo) on
equivalent expression, e.g. sum of two regs or even more complex expression. 
That is how such address can occur during LRA work.  But LRA should do all
necessary transformations to get the right address after all.


       reply	other threads:[~2014-06-05 13:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-61411-4@http.gcc.gnu.org/bugzilla/>
2014-06-05 13:54 ` vmakarov at gcc dot gnu.org [this message]
2014-06-06  6:51 ` amker.cheng at gmail dot com
2014-11-18 15:58 ` ramana 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-61411-4-nrYs83BIT2@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).