Re: java/2956: gcj does not terminate on invalid class definition

Re: java/2956: gcj does not terminate on invalid class definition

[mark]

Synopsis: gcj does not terminate on invalid class definition

State-Changed-From-To: feedback->closed
State-Changed-By: mark
State-Changed-When: Mon Oct 15 11:49:53 2001
State-Changed-Why:
    The bug does no longer exist with gcc from CVS
    (verified with gcc version 3.1 20011007)

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2956&database=gcc

Re: java/2956: gcj does not terminate on invalid class definition

[apbianco]

Synopsis: gcj does not terminate on invalid class definition

Responsible-Changed-From-To: unassigned->apbianco
Responsible-Changed-By: apbianco
Responsible-Changed-When: Wed Jul 18 14:15:46 2001
Responsible-Changed-Why:
    Mine.
State-Changed-From-To: open->feedback
State-Changed-By: apbianco
State-Changed-When: Wed Jul 18 14:15:46 2001
State-Changed-Why:
    I have a patch. I'm testing it at the moment and it should
    be fine. Note that if you're using 3.0, you get a bogus
    error message about cyclic inheritance. This is what this
    patch fixes.

http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view&pr=2956&database=gcc

java/2956: gcj does not terminate on invalid class definition

[mark]

>Number:         2956
>Category:       java
>Synopsis:       gcj does not terminate on invalid class definition
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat May 26 08:56:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     mark@klomp.org
>Release:        gcc version 3.0 20010526 (prerelease)
>Organization:
>Environment:

>Description:
gcj does not terminate when compiling the following class:

class BugObject extends Object;

It does generate an error message but after that just hangs.

$ gcj -C BugObject.java 
BugObject.java:1: '{' expected.
   class BugObject extends Object;
                                 ^

This does actually occur in the Jacks testsuite which means that we cannot run that testsuite since the test harness never kills the compiler.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: