public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: philb@gnu.org
To: gcc-gnats@gcc.gnu.org
Subject: target/2878: ARM: cannot use 3.0 to build stage 1 of bootstrap; bad code generated at -O0?
Date: Sun, 20 May 2001 03:36:00 -0000	[thread overview]
Message-ID: <20010520103345.24997.qmail@sourceware.cygnus.com> (raw)

>Number:         2878
>Category:       target
>Synopsis:       ARM: cannot use 3.0 to build stage 1 of bootstrap; bad code generated at -O0?
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun May 20 03:36:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     philb@gnu.org
>Release:        unknown-1.0
>Organization:
>Environment:

>Description:
Bootstrapping the 3.0 branch on arm-linux, using a compiler previously built from the same sources to build stage 1, eventually fails here:

./xgcc -B./ -B/usr/local/armv4l-unknown-linux-gnu/bin/ -isystem /usr/local/armv4l-unknown-linux-gnu/include -O2   -DIN_GCC    -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include  -fomit-frame-pointer -fPIC -g0 -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  -I. -I. -I/home/pb/egcs/3.0/gcc/gcc -I/home/pb/egcs/3.0/gcc/gcc/. -I/home/pb/egcs/3.0/gcc/gcc/config -I/home/pb/egcs/3.0/gcc/gcc/../include  -DL_bb -c /home/pb/egcs/3.0/gcc/gcc/libgcc2.c -o libgcc/./_bb.o
In file included from /home/pb/egcs/3.0/gcc/gcc/libgcc2.c:1298:
/home/pb/egcs/3.0/gcc/gcc/gcov-io.h: In function `__store_long':
/home/pb/egcs/3.0/gcc/gcc/gcov-io.h:67: Internal compiler error in canon_hash, at cse.c:2463
Please submit a full bug report, with preprocessed source if appropriate.
See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
make[3]: *** [libgcc/./_bb.o] Error 1

Since it works to use GCC 2.95 for building stage 1, it seems likely that GCC 3.0 is miscompiling itself at -O0.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-05-20  3:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-20  3:36 philb [this message]
2001-05-23 11:06 target/2878: ARM: cannot use 3.0 to build stage 1 of bootstrap;bad " Rod Stewart
2001-05-23 11:36 target/2878: ARM: cannot use 3.0 to build stage 1 of bootstrap; bad " Philip Blundell
2001-05-23 14:16 target/2878: ARM: cannot use 3.0 to build stage 1 of bootstrap;bad " Rod Stewart
2001-05-23 15:36 target/2878: ARM: cannot use 3.0 to build stage 1 of bootstrap; bad " Philip Blundell
2001-05-26 16:36 Philip Blundell
2001-06-08  6:09 nathan
2001-06-12  3:34 rearnsha
2001-06-13 10:27 mmitchel

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=20010520103345.24997.qmail@sourceware.cygnus.com \
    --to=philb@gnu.org \
    --cc=gcc-gnats@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).