From: Alexandre Oliva <aoliva@redhat.com>
To: Matthias Klose <doko@cs.tu-berlin.de>
Cc: gcc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, debian-gcc@lists.debian.org
Subject: Re: [3.3 branch] bootstrap failures on {arm,mips,mipsel,m68k}-linux
Date: Sat, 28 Dec 2002 10:05:00 -0000 [thread overview]
Message-ID: <oru1gy5g30.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <15885.47478.982833.769040@gargle.gargle.HOWL>
On Dec 28, 2002, Matthias Klose <doko@cs.tu-berlin.de> wrote:
> - latest try to build from CVS 20020907
> /tmp/ccs4dU7E.s: Assembler messages:
> /tmp/ccs4dU7E.s:28502: Error: Branch out of range
> [...]
> /tmp/ccs4dU7E.s:33314: Error: Branch out of range
This is a bug in the bootstrap compiler. There's nothing GCC 3.3 can
do about it. The bug is won't occur if you use GCC 3.3 as the
bootstrap compiler, since it's already fixed. You can build it
without bootstrapping and then use that for a bootstrap, or build
stage1 with optimization (STAGE1_CFLAGS='-O -g'), or use a CVS version
of binutils that supports branch relaxation in the assembler and
enable that by adding -Wa,--relax-branch to STAGE1_CFLAGS.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2002-12-28 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-28 9:59 Matthias Klose
2002-12-28 10:05 ` Alexandre Oliva [this message]
2002-12-29 8:32 ` Matthias Klose
2002-12-29 11:37 ` Alexandre Oliva
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=oru1gy5g30.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=debian-gcc@lists.debian.org \
--cc=doko@cs.tu-berlin.de \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc@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).