public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: pme@gcc.gnu.org
To: arndt.muehlenfeld@roche.com, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: c++/3749: gcc 3.0 crashes when compiling stc.cpp (see below)
Date: Fri, 19 Apr 2002 13:17:00 -0000 [thread overview]
Message-ID: <20020419201729.5118.qmail@sources.redhat.com> (raw)
Synopsis: gcc 3.0 crashes when compiling stc.cpp (see below)
State-Changed-From-To: open->closed
State-Changed-By: pme
State-Changed-When: Fri Apr 19 13:17:23 2002
State-Changed-Why:
With 3.1 20020418 (prerelease), I get no crash:
% g++ -fpreprocessed -c 3749_stc.cpp
The resulting .o will not link, of course, since the C++
library changed between 3.0 and 3.1, and stc.cpp is
already preprocessed.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3749
next reply other threads:[~2002-04-19 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 13:17 pme [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-20 9:16 arndt.muehlenfeld
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=20020419201729.5118.qmail@sources.redhat.com \
--to=pme@gcc.gnu.org \
--cc=arndt.muehlenfeld@roche.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).