public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: agx@sigxcpu.org
To: gcc-gnats@gcc.gnu.org
Cc: debian-gcc@lists.debian.org
Subject: bootstrap/10164: [linux-mips]: ICE while building libstdc++
Date: Thu, 20 Mar 2003 11:06:00 -0000	[thread overview]
Message-ID: <20030320110348.16126.qmail@sources.redhat.com> (raw)


>Number:         10164
>Category:       bootstrap
>Synopsis:       [linux-mips]: ICE while building libstdc++
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Thu Mar 20 11:06:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     agx@sigcpu.org
>Release:        gcc-ss-20030317
>Organization:
>Environment:
linux-mips SGI IP22 (debian unstable)
currently installed gcc is:
Reading specs from /usr/local/bin/../lib/gcc-lib/mips-unknown-linux-gnu/3.3/specs
Configured with: ../gcc-cvs/configure --prefix=/usr/local/stow/gcc-cvs-head --program-suffix=-cvs --enable-languages=c,c++ : (reconfigured) ../gcc-cvs/configure --prefix=/usr/local/stow/gcc-cvs-head --program-suffix=-cvs --enable-languages=c,c++
Thread model: posix
gcc version 3.3 20030310 (prerelease)
>Description:
when doing a native bootstrap 'make bootstrap' dies with a segmentation fault:

/import/gcc/gcc-cvs-build/gcc/xgcc -shared-libgcc -B/import/gcc/gcc-cvs-build/gcc/ -nostdinc++ -L/import/gcc/gcc-cvs-build/mips-unknown-linux-gnu/libstdc++-v3/src -L/import/gcc/gcc-cvs-build/mips-unknown-linux-gnu/libstdc++-v3/src/.libs -B/usr/local/stow/gcc-cvs-head/mips-unknown-linux-gnu/bin/ -B/usr/local/stow/gcc-cvs-head/mips-unknown-linux-gnu/lib/ -isystem /usr/local/stow/gcc-cvs-head/mips-unknown-linux-gnu/include -I../../../../gcc-cvs/libstdc++-v3/../gcc -I../../../../gcc-cvs/libstdc++-v3/../include -I/import/gcc/gcc-cvs-build/mips-unknown-linux-gnu/libstdc++-v3/include/mips-unknown-linux-gnu -I/import/gcc/gcc-cvs-build/mips-unknown-linux-gnu/libstdc++-v3/include -I../../../../gcc-cvs/libstdc++-v3/libsupc++ -g -O2 -D_GNU_SOURCE -fno-implicit-templates -Wall -Wno-format -W -Wwrite-strings -Winline -fdiagnostics-show-location=once -ffunction-sections -fdata-sections -c ../../../../gcc-cvs/libstdc++-v3/libsupc++/eh_alloc.cc  -fPIC -DPIC -o eh_alloc.o
In file included from ../../../../gcc-cvs/libstdc++-v3/libsupc++/eh_alloc.cc:33:
/import/gcc/gcc-cvs-build/mips-unknown-linux-gnu/libstdc++-v3/include/cstdlib: In
   function `lldiv_t __gnu_cxx::div(long long int, long long int)':
/import/gcc/gcc-cvs-build/mips-unknown-linux-gnu/libstdc++-v3/include/cstdlib:149: internal compiler error: Segmentation
   fault
>How-To-Repeat:
CC=gcc-cvs ../gcc-cvs/configure \
                        --program-suffix=-cvs   \
                        --enable-shared         \
                        --enable-threads        \
                        --enable-languages='c,c++,f77'

make bootstrap
>Fix:

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


             reply	other threads:[~2003-03-20 11:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 11:06 agx [this message]
2003-05-10  0:36 Dara Hazeghi
2003-05-10  7:49 giovannibajo
2003-05-10 16:06 Guido Guenther
2003-05-12 11:28 giovannibajo

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=20030320110348.16126.qmail@sources.redhat.com \
    --to=agx@sigxcpu.org \
    --cc=debian-gcc@lists.debian.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).