public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "laurent at guerby dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/44993]  New: [4.6 regression] sparc64-linux bootstrap broken
Date: Mon, 19 Jul 2010 16:14:00 -0000	[thread overview]
Message-ID: <bug-44993-7210@http.gcc.gnu.org/bugzilla/> (raw)

full 64 bit bootstrap is now failing:

r161903 ok
r161941 ko

/home/guerby/build/./gcc/xgcc -B/home/guerby/build/./gcc/
-B/n/62/guerby/install-trunk-64/sparc64-unknown-linux-gnu/bin/
-B/n/62/guerby/install-trunk-64/sparc64-unknown-linux-gnu/lib/ -isystem
/n/62/guerby/instal\
l-trunk-64/sparc64-unknown-linux-gnu/include -isystem
/n/62/guerby/install-trunk-64/sparc64-unknown-linux-gnu/sys-include    -c -g
-O2  -fPIC  -W -Wall -gnatpg   a-cdlili.adb -o a-cdlili.o
+===========================GNAT BUG DETECTED==============================+
| 4.6.0 20100708 (experimental) [trunk revision 161941]
(sparc64-unknown-linux-gnu) |
| Storage_Error stack overflow (or erroneous memory access)                |
| Error detected at s-finroo.ads:53:4                                      |

Then at r162274 there's a new earlier failure in bootstrap, probably masking
the above:

Comparing stages 2 and 3
warning: gcc/cc1-checksum.o differs
Bootstrap comparison failure!
gcc/dwarf2out.o differs
gcc/tree-ssa.o differs
libdecnumber/decNumber.o differs
libdecnumber/decimal32.o differs
libdecnumber/decimal64.o differs
libdecnumber/decimal128.o differs
make[2]: *** [compare] Error 1
make[2]: Leaving directory `/home/guerby/build'
make[1]: *** [stage3-bubble] Error 2
make[1]: Leaving directory `/home/guerby/build'
make: *** [bootstrap] Error 2

configure line:

export CC="gcc -m64"
../trunk/configure --prefix=/n/62/guerby/install-trunk-64 --disable-werror
--enable-languages=c,ada --enable-__cxa_atexit --disable-nls
--enable-threads=posix --with-mpfr=/opt/cfarm/mpfr-2.4.1-64
--with-gmp=/opt/cfarm/gmp-4.2.4-64 --with-mpc=/opt/cfarm/mpc-0.8-64


-- 
           Summary: [4.6 regression] sparc64-linux bootstrap broken
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: laurent at guerby dot net
 GCC build triplet: sparc64-unknown-linux-gnu
  GCC host triplet: sparc64-unknown-linux-gnu
GCC target triplet: sparc64-unknown-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44993


             reply	other threads:[~2010-07-19 16:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19 16:14 laurent at guerby dot net [this message]
2010-07-19 21:04 ` [Bug bootstrap/44993] " mikpe at it dot uu dot se
2010-07-24 21:43 ` ebotcazou at gcc dot gnu dot org
2010-07-24 21:44 ` ebotcazou at gcc dot gnu dot org
2010-07-27 20:16 ` ebotcazou at gcc dot gnu dot org
2010-07-28  7:45 ` [Bug middle-end/44993] " ebotcazou at gcc dot gnu dot org
2010-07-28  7:47 ` ebotcazou at gcc dot gnu dot 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-44993-7210@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).