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++/5665: gcc goes into endless loop on bad code
Date: Fri, 31 May 2002 08:16:00 -0000	[thread overview]
Message-ID: <20020531150601.18892.qmail@sources.redhat.com> (raw)

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

From: Reichelt <reichelt@igpm.rwth-aachen.de>
To: gcc-gnats@gcc.gnu.org, bergur@tern.is, gcc-bugs@gcc.gnu.org,
        nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/5665: gcc goes into endless loop on bad code
Date: Fri, 31 May 2002 17:35:40 +0200

 Hi,
 
 the PR can probably be closed, since with gcc 3.1 the problems seem to
 have been fixed. I.e. the compiler neither enters an endless loop (as
 gcc 3.0.3 did) nor issues an ICE (as development versions of 3.1 did).
 
 Greetings,
 Volker Reichelt
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5665
 
 


             reply	other threads:[~2002-05-31 15:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-31  8:16 Reichelt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-01  8:02 lerdsuwa
2002-02-12  7:46 Reichelt

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=20020531150601.18892.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).