public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eweddington at cso dot atmel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/31786] error: unable to find a register to spill in class 'BASE_POINTER_REGS'
Date: Thu, 03 May 2007 12:05:00 -0000 [thread overview]
Message-ID: <20070503120541.14267.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31786-8160@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from eweddington at cso dot atmel dot com 2007-05-03 13:05 -------
Subject: RE: error: unable to find a register to spill in
class 'BASE_POINTER_REGS'
> ------- Comment #2 from ralf_corsepius at rtems dot org
> 2007-05-03 10:27 -------
> I can also reproduce the bug with 4.2.0-20070501.
>
> It also is related to optimization levels. Newlib is being
> compiled with -O2,
> which triggers this breakdown. Using -O1 or -Os to build
> init.c lets the
> breakdown vanish.
>
> Eric, due to bugzilla's current brokenness, I am sending you
> the *.i on PM.
Hi Ralf,
All public distros use avr-libc instead of newlib to build an AVR toolchain:
<http://savannah.nongnu.org/projects/avr-libc>
AFAIK, it is only RTEMS that attempts to use newlib. And because of this the
only testing that is done is when you do it, so I'm not surprised that
newlib is broken for the avr.
Eric
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31786
next prev parent reply other threads:[~2007-05-03 12:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 13:14 [Bug target/31786] New: " ralf_corsepius at rtems dot org
2007-05-02 19:34 ` [Bug target/31786] " eweddington at cso dot atmel dot com
2007-05-03 9:27 ` ralf_corsepius at rtems dot org
2007-05-03 9:43 ` ralf_corsepius at rtems dot org
2007-05-03 12:05 ` eweddington at cso dot atmel dot com [this message]
2007-05-03 12:12 ` ralf dot corsepius at rtems dot org
2007-05-03 13:07 ` ralf_corsepius at rtems dot org
2007-05-03 14:21 ` ralf_corsepius at rtems dot org
2007-05-03 15:40 ` eweddington at cso dot atmel dot com
2007-05-04 15:06 ` eweddington at cso dot atmel dot com
2007-05-30 20:40 ` [Bug target/31786] [4.1/4.2/4.3 Regression][avr] " eweddington at cso dot atmel dot com
2007-06-10 16:43 ` eweddington at cso dot atmel dot com
2007-06-10 16:50 ` eweddington at cso dot atmel dot com
2007-07-04 3:06 ` mmitchel at gcc dot gnu dot org
2008-01-02 13:44 ` hutchinsonandy at netscape dot net
2008-01-02 23:46 ` hutchinsonandy at netscape dot net
2008-01-13 16:04 ` rguenth at gcc dot gnu dot org
2008-07-04 22:03 ` [Bug target/31786] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2008-09-14 12:53 ` aesok at gcc dot gnu dot org
2009-03-31 20:09 ` [Bug target/31786] [4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org
2009-08-04 12:39 ` rguenth at gcc dot gnu dot org
2010-01-29 17:46 ` [Bug target/31786] [avr] " eric dot weddington at atmel 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=20070503120541.14267.qmail@sourceware.org \
--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).