public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: peter.karl.mueller@gmx.de
To: gcc-gnats@gcc.gnu.org
Cc: peter.karl.mueller@gmx.de
Subject: c++/8523: gcc 3.2 hang after parse error
Date: Sun, 10 Nov 2002 21:56:00 -0000 [thread overview]
Message-ID: <20021111053935.4506D16464@amd386.local> (raw)
>Number: 8523
>Category: c++
>Synopsis: gcc 3.2 hang after parse error (C++)
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Nov 10 21:56:02 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Peter Karl Mueller
>Release: 3.2
>Organization:
No-Org
>Environment:
System: Linux XXXXXX 2.4.16-4GB #1 Mit Okt 30 14:20:02 CET 2002 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-3.2/configure --prefix=/usr5/xhome/softw1/install-3.2 --enable-threads --enable-shared
>Description:
After detecting the parse error gcc hangs.
>How-To-Repeat:
g++ 1.cc
FILE 1.cc:
1 struct s {
2 void f ()
3 {
4 double t;
5 for (int i = 2; i >= 0; --i)
6 t +=
7 }
8 };
>Fix:
correct the example :-)
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2002-11-11 5:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021111053935.4506D16464@amd386.local \
--to=peter.karl.mueller@gmx.de \
--cc=gcc-gnats@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).