From: Graham Stott <graham.stott@btinternet.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: gcc@gcc.gnu.org
Subject: Re: AIX bootstrap failure
Date: Tue, 01 Oct 2002 10:17:00 -0000 [thread overview]
Message-ID: <3D99D88A.10007@btinternet.com> (raw)
In-Reply-To: <200210011646.MAA23246@makai.watson.ibm.com>
David,
David Edelsohn wrote:
> Bootstrap failed on AIX with GCC 3.3 20021001 experimental updated:
>
> Tue Oct 1 10:45:47 EDT 2002
> Tue Oct 1 14:45:47 UTC 2002
>
> /gcc/dje/build/powerpc-ibm-aix4.3.3.0-20021001/gcc/xgcc -shared-libgcc -B/gcc/dje/build/powerpc-ibm-aix4.3.3.0-20021001/gcc/ -nostdinc++ -L/gcc/dje/build/powerpc-ibm-aix4.3.3.0-20021001/powerpc-ibm-aix4.3.3.0/ppc64/libstdc++-v3/src -L/gcc/dje/build/powerpc-ibm-aix4.3.3.0-20021001/powerpc-ibm-aix4.3.3.0/ppc64/libstdc++-v3/src/.libs -B/gcc/dje/install/powerpc-ibm-aix4.3.3.0-20021001/powerpc-ibm-aix4.3.3.0/bin/ -B/gcc/dje/install/powerpc-ibm-aix4.3.3.0-20021001/powerpc-ibm-aix4.3.3.0/lib/ -isystem /gcc/dje/install/powerpc-ibm-aix4.3.3.0-20021001/powerpc-ibm-aix4.3.3.0/include -maix64 -nostdinc++ -I/gcc/dje/build/powerpc-ibm-aix4.3.3.0-20021001/powerpc-ibm-aix4.3.3.0/ppc64/libstdc++-v3/include/powerpc-ibm-aix4.3.3.0 -I/gcc/dje/build/powerpc-ibm-aix4.3.3.0-20021001/powerpc-ibm-aix4.3.3.0/ppc64/libstdc++-v3/include -I/gcc/dje/src/libstdc++-v3/libsupc++ -I/gcc/dje/src/libstdc++-v3/libmath -g -O2 -maix64 -fno-implicit-templates -Wall -Wno-format -W -Wwrite-strings -Winline -fdiagno
s!
> tics-show-location=once -ffunction-sections -fdata-sections -g -c /gcc/dje/src/libstdc++-v3/src/localename.cc -DPIC -o .libs/localename.o
>
> /gcc/dje/src/libstdc++-v3/src/localename.cc: In member function `void
> std::locale::_Impl::_M_replace_categories(const std::locale::_Impl*,
> unsigned int)':
> /gcc/dje/src/libstdc++-v3/src/localename.cc:219: internal compiler error: in
> int_mode_for_mode, at stor-layout.c:292
>
> int_mode_for_mode is being invoked with the argument of GET_MODE (op0)
>
> op0 is (mem/s/u (reg/f:DI 131) [68 _S_facet_categories A8])
>
>
This also fails on nearly all the cross compilers I'm building do you have any idea
when it got introduced? I've been alway for 3 weeks and updated my tree yesterday.
so I don't know when it first appeared other than sometime in the last 3 weeks.
Cheers
Graham
next prev parent reply other threads:[~2002-10-01 17:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 9:46 David Edelsohn
2002-10-01 10:17 ` Graham Stott [this message]
2002-10-01 11:01 ` David Edelsohn
2002-10-01 12:03 ` Mark Mitchell
2002-10-01 13:33 ` David Edelsohn
2002-10-01 15:33 ` Mark Mitchell
-- strict thread matches above, loose matches on Subject: below --
2005-05-18 13:51 David Edelsohn
2004-09-29 18:01 jlquinn
2004-09-29 18:04 ` David Edelsohn
2004-10-01 0:41 ` Jerry Quinn
2004-10-01 1:25 ` David Edelsohn
2003-03-07 16:35 David Edelsohn
2002-10-01 16:28 John David Anglin
2002-10-01 22:23 ` Loren James Rittle
2002-10-01 16:05 Mark Mitchell
2002-10-01 16:07 ` David Edelsohn
2002-10-01 16:48 ` Mark Mitchell
[not found] <10111111037.AA01266@vlsi1.ultra.nyu.edu>
2001-11-01 8:30 ` Aldy Hernandez
1997-11-06 2:18 Dave Love
1997-11-06 8:33 ` David Edelsohn
1997-11-06 10:18 ` Dave Love
1997-11-06 9:18 ` Jeffrey A Law
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=3D99D88A.10007@btinternet.com \
--to=graham.stott@btinternet.com \
--cc=dje@watson.ibm.com \
--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).