public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/54814] [4.8 Regression] ICE: unable to find a register to spill in class 'R0_REG'
Date: Fri, 07 Dec 2012 13:35:00 -0000	[thread overview]
Message-ID: <bug-54814-4-PSkPz8Oq99@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54814-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #2 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2012-12-07 13:34:36 UTC ---
rguenth at gcc dot gnu.org wrote:
>  spill in class 'R0_REG'

Spilling is a bug in the register allocator, or am I missing something.

Besides that, I am getting this mail because I am CCed to PR54814
but your comment

  spill in class 'R0_REG'

is missing in PR54814 so nobody can really follow what is going on for what
reason.

Johann

> 
> Date: Fri, 07 Dec 2012 11:46:42 +0000
> 
> X-Bugzilla-Reason: Reporter
> 
> X-Bugzilla-Type: changed
> 
> X-Bugzilla-Watch-Reason: None
> 
> X-Bugzilla-Product: gcc
> 
> X-Bugzilla-Component: other
> 
> X-Bugzilla-Keywords: ice-on-valid-code, ra
> 
> X-Bugzilla-Severity: normal
> 
> X-Bugzilla-Who: rguenth at gcc dot gnu.org
> 
> X-Bugzilla-Status: NEW
> 
> X-Bugzilla-Priority: P4
> 
> X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
> 
> X-Bugzilla-Target-Milestone: 4.8.0
> 
> X-Bugzilla-Changed-Fields: Priority
> 
> Message-ID: <bug-54814-20453-4HTXOBm3vX@http.gcc.gnu.org/bugzilla/>
> 
> In-Reply-To: <bug-54814-20453@http.gcc.gnu.org/bugzilla/>
> 
> References: <bug-54814-20453@http.gcc.gnu.org/bugzilla/>
> 
> X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
> 
> Auto-Submitted: auto-generated
> 
> Content-Type: text/plain; charset="UTF-8"
> 
> MIME-Version: 1.0
> 
> 
> 
> 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54814
> 
> 
> 
> Richard Biener <rguenth at gcc dot gnu.org> changed:
> 
> 
> 
>            What    |Removed                     |Added
> 
> ----------------------------------------------------------------------------
> 
>            Priority|P3                          |P4
> 
> 
>


  parent reply	other threads:[~2012-12-07 13:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04 17:17 [Bug other/54814] New: " gjl at gcc dot gnu.org
2012-10-14 11:15 ` [Bug other/54814] " gjl at gcc dot gnu.org
2012-11-25 15:55 ` rguenth at gcc dot gnu.org
2012-12-07 11:46 ` rguenth at gcc dot gnu.org
2012-12-07 13:35 ` gjl at gcc dot gnu.org [this message]
2012-12-07 17:59 ` gjl at gcc dot gnu.org
2012-12-07 22:03 ` steven at gcc dot gnu.org
2012-12-07 22:41 ` steven at gcc dot gnu.org
2012-12-07 22:51 ` steven at gcc dot gnu.org
2012-12-08 10:28 ` gjl at gcc dot gnu.org
2012-12-08 13:17 ` steven at gcc dot gnu.org
2012-12-08 14:09 ` bernds at gcc dot gnu.org
2012-12-10 14:33 ` gjl at gcc dot gnu.org
2012-12-14 18:56 ` gjl at gcc dot gnu.org
2012-12-18  4:50 ` bernds at gcc dot gnu.org
2012-12-18 22:34 ` gjl at gcc dot gnu.org
2013-01-25 20:56 ` gjl at gcc dot gnu.org
2013-01-28 20:04 ` gjl at gcc dot gnu.org
2013-01-28 20:06 ` gjl 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-54814-4-PSkPz8Oq99@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).