public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "robert.suchanek at imgtec dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/59317] [4.9 Regression] [LRA,MIPS] ICE: in check_rtl, at lra.c (insn does not satisfy constraints)
Date: Wed, 04 Dec 2013 12:02:00 -0000	[thread overview]
Message-ID: <bug-59317-4-H9rNT5eyLP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59317-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59317

--- Comment #2 from Robert Suchanek <robert.suchanek at imgtec dot com> ---
The latest patches do not seem to resolve the issue.

Although the newly generated pseudos get ALL_REGS class assigned, the class
change does not happen later. As the class is not changed, hard regs are found
basing on the class, and hence, wrong hard reg(s) are assigned and it is found
by the coherency check.

If I'm right, there are least two opportunities where the class can be changed
in the constraint pass. One fails as the constraints cannot influence the
classes of the new pseudos (for reload insns) and another one when it tries to
narrow the class for input pseudos.


  parent reply	other threads:[~2013-12-04 12:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27 16:14 [Bug rtl-optimization/59317] New: " robert.suchanek at imgtec dot com
2013-11-28 11:38 ` [Bug rtl-optimization/59317] " rguenth at gcc dot gnu.org
2013-12-03 23:08 ` vmakarov at gcc dot gnu.org
2013-12-04 12:02 ` robert.suchanek at imgtec dot com [this message]
2013-12-04 16:13 ` vmakarov at gcc dot gnu.org
2013-12-05 10:06 ` robert.suchanek at imgtec dot com
2013-12-05 10:08 ` robert.suchanek at imgtec dot com
2013-12-05 19:39 ` vmakarov at gcc dot gnu.org
2013-12-06  9:41 ` robert.suchanek at imgtec dot com

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-59317-4-H9rNT5eyLP@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).