From: Ramana Radhakrishnan <ramana.r@gmail.com>
To: Michael Matz <matz@suse.de>
Cc: gcc@gcc.gnu.org
Subject: Re: ra.c todo list.
Date: Thu, 09 Sep 2004 19:13:00 -0000 [thread overview]
Message-ID: <67ea2eb04090912034440bc2a@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0409061752050.20630@wotan.suse.de>
Hi,
As I had promised, but while building the new-regalloc-branch and the
C++ compiler during the build there is an ICE . The error message is
given below. . I was not able to find any equivalent error on Google.
Making all in src
make[3]: Entering directory
`/home/ramana/toolscvs/reg-alloc-branch/build-all/i686-pc-linux-gnu/libstdc++-v3/src'
/bin/sh ../libtool --tag CXX --mode=compile
/home/ramana/toolscvs/reg-alloc-branch/build-all/gcc/xgcc
-shared-libgcc -B/home/ramana/toolscvs/reg-alloc-branch/build-all/gcc/
-nostdinc++ -L/home/ramana/toolscvs/reg-alloc-branch/build-all/i686-pc-linux-gnu/libstdc++-v3/src
-L/home/ramana/toolscvs/reg-alloc-branch/build-all/i686-pc-linux-gnu/libstdc++-v3/src/.libs
-B/usr/local/i386-regalloc-branch/i686-pc-linux-gnu/bin/
-B/usr/local/i386-regalloc-branch/i686-pc-linux-gnu/lib/ -isystem
/usr/local/i386-regalloc-branch/i686-pc-linux-gnu/include -isystem
/usr/local/i386-regalloc-branch/i686-pc-linux-gnu/sys-include
-I/home/ramana/toolscvs/reg-alloc-branch/build-all/i686-pc-linux-gnu/libstdc++-v3/include/i686-pc-linux-gnu
-I/home/ramana/toolscvs/reg-alloc-branch/build-all/i686-pc-linux-gnu/libstdc++-v3/include
-I/home/ramana/toolscvs/reg-alloc-branch/gcc/libstdc++-v3/libsupc++
-O2 -pg -g -g -O2 -D_GNU_SOURCE -fno-implicit-templates -Wall -W
-Wwrite-strings -Wcast-qual -fdiagnostics-show-location=once
-fimplicit-templates -c ../../../../gcc/libstdc++-v3/src/demangle.cc
/home/ramana/toolscvs/reg-alloc-branch/build-all/gcc/xgcc
-shared-libgcc -B/home/ramana/toolscvs/reg-alloc-branch/build-all/gcc/
-nostdinc++ -L/home/ramana/toolscvs/reg-alloc-branch/build-all/i686-pc-linux-gnu/libstdc++-v3/src
-L/home/ramana/toolscvs/reg-alloc-branch/build-all/i686-pc-linux-gnu/libstdc++-v3/src/.libs
-B/usr/local/i386-regalloc-branch/i686-pc-linux-gnu/bin/
-B/usr/local/i386-regalloc-branch/i686-pc-linux-gnu/lib/ -isystem
/usr/local/i386-regalloc-branch/i686-pc-linux-gnu/include -isystem
/usr/local/i386-regalloc-branch/i686-pc-linux-gnu/sys-include
-I/home/ramana/toolscvs/reg-alloc-branch/build-all/i686-pc-linux-gnu/libstdc++-v3/include/i686-pc-linux-gnu
-I/home/ramana/toolscvs/reg-alloc-branch/build-all/i686-pc-linux-gnu/libstdc++-v3/include
-I/home/ramana/toolscvs/reg-alloc-branch/gcc/libstdc++-v3/libsupc++
-O2 -pg -g -g -O2 -D_GNU_SOURCE -fno-implicit-templates -Wall -W
-Wwrite-strings -Wcast-qual -fdiagnostics-show-location=once
-fimplicit-templates -c ../../../../gcc/libstdc++-v3/src/demangle.cc
-fPIC -DPIC
/home/ramana/toolscvs/reg-alloc-branch/build-all/i686-pc-linux-gnu/libstdc++-v3/include/bits/stl_uninitialized.h:
In function `_ForwardIterator
std::__uninitialized_copy_aux(_InputIterator, _InputIterator,
_ForwardIterator, __false_type) [with _InputIterator =
__gnu_cxx::__normal_iterator<__gnu_cxx::demangler::substitution_st*,
std::vector<__gnu_cxx::demangler::substitution_st,
std::allocator<char> > >, _ForwardIterator =
__gnu_cxx::__normal_iterator<__gnu_cxx::demangler::substitution_st*,
std::vector<__gnu_cxx::demangler::substitution_st,
std::allocator<char> > >]':
/home/ramana/toolscvs/reg-alloc-branch/build-all/i686-pc-linux-gnu/libstdc++-v3/include/bits/stl_uninitialized.h:600:
internal compiler error: Segmentation fault
Any ideas / comments. ?
cheers
Ramana
--
Ramana Radhakrishnan
next parent reply other threads:[~2004-09-09 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <67ea2eb040905020128b03316@mail.gmail.com>
[not found] ` <Pine.LNX.4.58.0409060926360.20630@wotan.suse.de>
[not found] ` <67ea2eb040906011154bb737b@mail.gmail.com>
[not found] ` <Pine.LNX.4.58.0409061752050.20630@wotan.suse.de>
2004-09-09 19:13 ` Ramana Radhakrishnan [this message]
2004-09-09 19:17 ` Michael Matz
2004-09-10 6:01 ` [Patch]fix new reg-alloc-branch crash in final.c Ramana Radhakrishnan
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=67ea2eb04090912034440bc2a@mail.gmail.com \
--to=ramana.r@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=matz@suse.de \
/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).