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 target/52575] avr*: error: unable to find a register to spill in class 'POINTER_REGS
Date: Thu, 15 Mar 2012 12:54:00 -0000 [thread overview]
Message-ID: <bug-52575-4-v6lQjCO8kS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52575-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52575
--- Comment #4 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2012-03-15 12:14:56 UTC ---
(In reply to comment #3)
> (In reply to comment #2)
> > There are already spill fails reported for AVR, it's a known problem.
> >
> > At this point it cannot be said if this PR is really the same as PR50925,
> > but it's not unlikely.
>
> I am confused:
>
> PR50925 says "fails to build 4.6.2", however avr-rtems-gcc4.6.2 and 4.6.3 are
> known to build,
These spill fails might come or go with slight variations in surrounding code,
compiler source (i.e. version) or change of compiler options. The absence of a
spill fail does not mean that it is not present in the compiler, it just means
it does not show with that specific test case and set of options.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50925#c19
test case breaks 4.5, 4.6, 4.7 and 4.8 for example.
PR42204 indicates that the problem occurs with framepointer needed/framepointer
not needed transitions and changing back and forth. Such transitions depend on
the surrounding code and compiler optimizations, of course.
PR52148 is a bit different: The root cause is the same. But a code cleanup made
the test case pass. Therefore it's not marked as a duplicate, even though it's
very likely that its root cause is also the same as in PR50925. However, the
code cleanup along with PR52148 does not fix the root cause; it's just a
cleanup that's nice in itself.
prev parent reply other threads:[~2012-03-15 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 6:29 [Bug target/52575] New: " ralf_corsepius at rtems dot org
2012-03-13 8:12 ` [Bug target/52575] " ralf_corsepius at rtems dot org
2012-03-13 9:44 ` gjl at gcc dot gnu.org
2012-03-13 17:01 ` ralf_corsepius at rtems dot org
2012-03-15 12:54 ` gjl at gcc dot gnu.org [this message]
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-52575-4-v6lQjCO8kS@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).