public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Michael Ritzert <michael.ritzert@realtech.de>
To: geoffk@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9304: [pch] ICE in gen_subprogram_die
Date: Wed, 05 Feb 2003 10:16:00 -0000	[thread overview]
Message-ID: <20030205101601.25390.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/9304; it has been noted by GNATS.

From: Michael Ritzert <michael.ritzert@realtech.de>
To: gcc-gnats@gcc.gnu.org, geoffk@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: c++/9304: [pch] ICE in gen_subprogram_die
Date: Wed, 5 Feb 2003 11:13:30 +0100

 Important info: The error on the testcase in the bugreport only appears o=
 n=20
 Debian GNU/Linux unstable, but not on SuSE Linux 7.3 (using identical=20
 versions of gcc). So if you can't reproduce it, it is likely due to a=20
 different environment.
 
 If somebody wants to try and reproduce the error, just ask me in private =
 mail=20
 to produce another preprocessed testcase. For some reason I can no longer=
 =20
 compile the one in the bugreport (StdAfx.h:18891: error:=20
 `_M_c_locale_codecvt' has not been declared) - propably because of the=20
 stricter parser.
 
 Michael
 


             reply	other threads:[~2003-02-05 10:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05 10:16 Michael Ritzert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-23 18:00 geoffk
2003-04-22 17:36 Geoffrey Keating
2003-04-22 17:29 geoffk
2003-02-04 23:56 Michael Ritzert
2003-02-04 23:30 geoffk
2003-02-04 22:54 bangerth
2003-02-04 22:26 Michael Ritzert
2003-02-04 18:56 Michael Ritzert
2003-02-04 18:46 Michael Ritzert
2003-02-04 14:46 Wolfgang Bangerth
2003-02-04 11:06 Michael Ritzert
2003-02-03 18:26 Michael Ritzert
2003-02-01 21:03 bangerth
2003-01-14 11:36 ritzert

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=20030205101601.25390.qmail@sources.redhat.com \
    --to=michael.ritzert@realtech.de \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=geoffk@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).