public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olh at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/12787] New: libsupc++/tinfo2.cc:167: internal compiler error: in output_die, at dwarf2out.c:6652
Date: Mon, 27 Oct 2003 09:11:00 -0000 [thread overview]
Message-ID: <20031027090951.12787.olh@suse.de> (raw)
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12787
Summary: libsupc++/tinfo2.cc:167: internal compiler error: in
output_die, at dwarf2out.c:6652
Product: gcc
Version: 3.4
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bootstrap
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: olh at suse dot de
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: powerpc-linux
GCC host triplet: powerpc-linux
GCC target triplet: powerpc-linux
toolchain:~/obj34/obj-gcc/powerpc-unknown-linux-gnu/nof/libstdc++-v3/libsupc++ $ /home/toolchain/obj34/obj-gcc/gcc/cc1plus -fpreprocessed tinfo2.ii -quiet -dumpbase tinfo2.cc -msoft-float -mstrict-align -msoft-float -mstrict-align -auxbase-strip tinfo2.o -g -g -O2 -O1 -O1 -Wall -Wall -Wall -W -Wwrite-strings -Wcast-qual -version -fPIC -fsigned-char -fmessage-length=0 -fsigned-char -fmessage-length=0 -fPIC -fno-implicit-templates -fdiagnostics-show-location=once -fPIC -o tinfo2.s
GNU C++ version 3.4 20031027 (experimental) (powerpc-unknown-linux-gnu)
compiled by GNU C version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice).
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
/home/toolchain/src/gcc-head/libstdc++-v3/libsupc++/tinfo2.cc:167: internal compiler error: in output_die, at dwarf2out.c:6652
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
next reply other threads:[~2003-10-27 9:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 9:11 olh at suse dot de [this message]
2003-10-27 9:49 ` [Bug bootstrap/12787] " olh at suse dot de
2003-10-27 17:19 ` olh at suse dot de
2003-10-30 5:42 ` pinskia at gcc dot gnu dot org
2003-10-30 13:48 ` olh at suse dot de
2003-10-30 17:23 ` pinskia at gcc dot gnu dot org
2003-10-30 18:32 ` olh at suse dot de
2003-10-30 20:56 ` olh at suse dot de
2003-10-31 9:48 ` olh at suse dot de
2003-11-01 11:53 ` olh at suse dot de
2003-11-01 12:01 ` olh at suse dot de
2003-11-02 22:51 ` [Bug debug/12787] [3.4 Regression] [unit-at-a-time] " pinskia at gcc dot gnu dot org
2003-12-19 6:00 ` pinskia at gcc dot gnu dot org
2003-12-29 12:06 ` hubicka at gcc dot gnu dot org
2004-01-02 12:50 ` olh at suse dot de
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=20031027090951.12787.olh@suse.de \
--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).