public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org
To: bkoz@redhat.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	geoffk@gcc.gnu.org, geoffk@geoffk.org, jason@redhat.com,
	pcarlini@unitus.it
Subject: Re: other/9274: [pch] cannot create libstdc++-v3 pch
Date: Mon, 14 Apr 2003 19:16:00 -0000	[thread overview]
Message-ID: <20030414191624.16038.qmail@sources.redhat.com> (raw)

Synopsis: [pch] cannot create libstdc++-v3 pch

State-Changed-From-To: analyzed->open
State-Changed-By: bkoz
State-Changed-When: Mon Apr 14 19:16:24 2003
State-Changed-Why:
    
    I've re-tested this with:
    
    xgcc (GCC) 3.4 20030413 (experimental)
    
    And am still seeing the failure reported previously.
    
    /mnt/hd/src/gcc/libstdc++-v3/testsuite/22_locale/money_get/get/char/wrapped_env.cc:71: internal compiler error: in gen_subprogram_die, at dwarf2out.c:10899
    
    Please submit a full bug report,
     with preprocessed source if appropriate
    
    So. I've attached the precompiled includes with this email, but I'm not quite sure if this still is useful, with PCH on.
    
    -benjamin

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9274


             reply	other threads:[~2003-04-14 19:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14 19:16 bkoz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-16  0:30 geoffk
2003-04-15 22:56 Paolo Carlini
2003-04-15 22:46 Benjamin Kosnik
2003-04-15 20:56 Geoff Keating
2003-04-15 15:46 Benjamin Kosnik
2003-04-14 22:06 Geoff Keating
2003-04-10 21:51 bkoz
2003-03-25 18:06 bkoz
2003-02-22  0:46 Geoffrey Keating
2003-02-06 21:25 bkoz

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=20030414191624.16038.qmail@sources.redhat.com \
    --to=bkoz@gcc.gnu.org \
    --cc=bkoz@redhat.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=geoffk@gcc.gnu.org \
    --cc=geoffk@geoffk.org \
    --cc=jason@redhat.com \
    --cc=pcarlini@unitus.it \
    /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).