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] New: [4.8 Regression] ICE: unable to find a register to spill in class 'R0_REG' Date: Thu, 04 Oct 2012 17:17:00 -0000 [thread overview] Message-ID: <bug-54814-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54814 Bug #: 54814 Summary: [4.8 Regression] ICE: unable to find a register to spill in class 'R0_REG' Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Keywords: ice-on-valid-code, ra Severity: normal Priority: P3 Component: other AssignedTo: unassigned@gcc.gnu.org ReportedBy: gjl@gcc.gnu.org CC: eric.weddington@atmel.com Target: avr Created attachment 28358 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28358 spills.txt: Hundreds of Spill Fails The testsuit throws hundreds of spill fails when running against the avr cross compiler. The testsuite used to produce about ~5 spill fails with avr-gcc. The strange with these spill fails is that they report register class RO_REG which contains just one fixed register. ./gcc/testsuite/gcc.c-torture/compile/20010426-1.c:19:1: error: unable to find a register to spill in class 'R0_REG' ./gcc/testsuite/gcc.c-torture/compile/20040121-1.c:41:1: error: unable to find a register to spill in class 'R0_REG' ... For a complete list see attachment. == configure == SVN trunk r192090 from today (2012-10-04) $ ../../gcc.gnu.org/trunk/configure --target=avr --prefix=/local/gnu/install/gcc-4.8 --disable-nls --with-dwarf2 --enable-target-optspace=yes --enable-languages=c,c++
next reply other threads:[~2012-10-04 17:17 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-04 17:17 gjl at gcc dot gnu.org [this message] 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 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@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: linkBe 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).