public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/12787] libsupc++/tinfo2.cc:167: internal compiler error: in output_die, at dwarf2out.c:6652
Date: Thu, 30 Oct 2003 05:42:00 -0000	[thread overview]
Message-ID: <20031030053707.6767.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031027090951.12787.olh@suse.de>

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


pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING


------- Additional Comments From pinskia at gcc dot gnu dot org  2003-10-30 05:37 -------
You only did "make" instead of "make bootstrap", what happens if you do "make bootstrap", do this 
ICE still happen, if not then your compiler you using to build is generating wrong code.


  parent reply	other threads:[~2003-10-30  5:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27  9:11 [Bug bootstrap/12787] New: " olh at suse dot de
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 [this message]
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=20031030053707.6767.qmail@sources.redhat.com \
    --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).