public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: paolo@gcc.gnu.org
To: dv@vollmann.ch, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c++/8338: [3_2 and mainline regression from 3.0.x] Infinite loop on illegal code
Date: Sun, 27 Oct 2002 01:46:00 -0000	[thread overview]
Message-ID: <20021027084656.31956.qmail@sources.redhat.com> (raw)

Old Synopsis: Koenig lookup doesn't find enum value in special case
New Synopsis: [3_2 and mainline regression from 3.0.x] Infinite loop on illegal code

State-Changed-From-To: open->analyzed
State-Changed-By: paolo
State-Changed-When: Sun Oct 27 01:46:55 2002
State-Changed-Why:
    During the compilation of the first testcase (*not* that
    provided later in the audit trail) both 3_2 and mainline
    loop forever and consume an enormous amount of memory after
    having output:
    8338.cc: In instantiation of `N2::A<N1::E, N1::Alias>':
    8338.cc:34:   instantiated from here
    8338.cc:15: `max' was not declared in this scope
    
    This is a regression from 3.0.x (2.95.x ICEd).

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8338


                 reply	other threads:[~2002-10-27  8:46 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=20021027084656.31956.qmail@sources.redhat.com \
    --to=paolo@gcc.gnu.org \
    --cc=dv@vollmann.ch \
    --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).