public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Reichelt <reichelt@igpm.rwth-aachen.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8067: g++ 3.2 internal error: Segmentation fault
Date: Mon, 30 Sep 2002 09:56:00 -0000 [thread overview]
Message-ID: <20020930165602.30088.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/8067; it has been noted by GNATS.
From: Reichelt <reichelt@igpm.rwth-aachen.de>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
y_fedor@ciam.ru
Cc:
Subject: Re: c++/8067: g++ 3.2 internal error: Segmentation fault
Date: Mon, 30 Sep 2002 19:35:23 +0200
Hi,
the problem can be demonstated with just a single line of (legal) code:
------------------snip here---------------------
void foo() { for ( __PRETTY_FUNCTION__ ; ; ) ; }
------------------snip here---------------------
The error (using gcc 3.1, 3.2 or the main trunk) is
(checked on mips-sgi-irix6.5 and i686-pc-linux-gnu):
PR8067.cc: In function `void foo()':
PR8067.cc:1: internal error: Segmentation fault
Please submit a full bug report, [etc.]
Since the code compiles fine with gcc 3.0.x, this is a regression.
Thus, the PR should be marked "high priority".
Greetings,
Volker Reichelt
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8067
next reply other threads:[~2002-09-30 16:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 9:56 Reichelt [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-23 17:14 mmitchel
2002-10-23 15:06 mmitchel
2002-10-07 14:26 Pop Sébastian
2002-10-06 12:16 Gabriel Dos Reis
2002-10-06 12:06 Pop Sébastian
2002-10-04 11:46 Jason Merrill
2002-09-30 13:06 Pop Sébastian
2002-09-30 10:36 Pop Sébastian
2002-09-28 6:32 lerdsuwa
2002-09-27 0:06 y_fedor
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=20020930165602.30088.qmail@sources.redhat.com \
--to=reichelt@igpm.rwth-aachen.de \
--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).