public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c++/5665: gcc goes into endless loop on bad code
@ 2002-06-01  8:02 lerdsuwa
  0 siblings, 0 replies; 3+ messages in thread
From: lerdsuwa @ 2002-06-01  8:02 UTC (permalink / raw)
  To: bergur, gcc-bugs, gcc-prs, nobody

Synopsis: gcc goes into endless loop on bad code

State-Changed-From-To: open->analyzed
State-Changed-By: lerdsuwa
State-Changed-When: Sat Jun  1 08:02:02 2002
State-Changed-Why:
    Confirmed.  I still have an ICE on the main trunk though.

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: c++/5665: gcc goes into endless loop on bad code
@ 2002-05-31  8:16 Reichelt
  0 siblings, 0 replies; 3+ messages in thread
From: Reichelt @ 2002-05-31  8:16 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

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
 
 


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: c++/5665: gcc goes into endless loop on bad code
@ 2002-02-12  7:46 Reichelt
  0 siblings, 0 replies; 3+ messages in thread
From: Reichelt @ 2002-02-12  7:46 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

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: Tue, 12 Feb 2002 17:06:04 +0100

 Hi,
 
 with gcc 3.1 20020202 (experimental) the code causes an ICE:
 
 [deleted lots of error messages]
 calc/fdps.h:865: parse error before `)' token
 calc/fdps.h:881: 'db_t' is used as a type, but is not defined as a type.
 calc/fdps.h:905: syntax error before `<' token
 calc/fdps.h:905: `MSG' was not declared in this scope
 calc/fdps.h:905: template argument 1 is invalid
 calc/fdps.h:905: tree check: expected class 't', have 'x' (error_mark) in 
    make_typename_type, at cp/decl.c:5689
 Please submit a full bug report, [etc.]
 
 The ICE can be reproduced with the following code snippet:
 
 ------------------snip here-----------------
 template<class T> class A
 {
     class B { X foo(); }; // illegal, X is undefined
 };
 
 template<class T> X A<T>::B::foo() {}
 ------------------snip here-----------------
 
 Just compile with "g++ -c" to the the following error message:
 
 bug.cpp:3: parse error before `)' token
 bug.cpp:6: syntax error before `<' token
 bug.cpp:6: `T' was not declared in this scope
 bug.cpp:6: template argument 1 is invalid
 bug.cpp:6: tree check: expected class 't', have 'x' (error_mark) in 
    make_typename_type, at cp/decl.c:5689
 Please submit a full bug report, [etc.]
 
 However, this reduced example compiles fine with gcc 3.0.3, i.e.
 a correct error message is emitted without ICE.
 
 Greetings,
 Volker Reichelt
 
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5665
 
 


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-06-01 15:02 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-06-01  8:02 c++/5665: gcc goes into endless loop on bad code lerdsuwa
  -- strict thread matches above, loose matches on Subject: below --
2002-05-31  8:16 Reichelt
2002-02-12  7:46 Reichelt

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