Re: java/1314: Multiple empty instance initializers put compiler into endless malloc loop

Re: java/1314: Multiple empty instance initializers put compiler into endless malloc loop

[apbianco]

Synopsis: Multiple empty instance initializers put compiler into endless malloc loop

State-Changed-From-To: open->feedback
State-Changed-By: apbianco
State-Changed-When: Wed Jun 27 15:50:16 2001
State-Changed-Why:
    I have a patch that I'll check in shortly.

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

Re: java/1314: Multiple empty instance initializers put compiler into endless malloc loop

[bryce]

Synopsis: Multiple empty instance initializers put compiler into endless malloc loop

State-Changed-From-To: feedback->closed
State-Changed-By: bryce
State-Changed-When: Sat Sep 29 22:53:32 2001
State-Changed-Why:
    Fixed in mainline. Thanks.

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

java/1314: Multiple empty instance initializers put compiler into endless malloc loop

[bryce]

>Number:         1314
>Category:       java
>Synopsis:       Multiple empty instance initializers put compiler into endless malloc loop
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apbianco
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Dec 20 12:18:57 PST 2000
>Closed-Date:    
>Last-Modified:  
>Originator:     Bryce McKinlay
>Release:        gcc version 2.96 20000722 (experimental)
>Organization:
>Environment:
any
>Description:
Attempt to compile the following (legal!) code results in 
jc1 trying to consume all memory:

class Skanky
{
  {
  }
  
  {
  }
}

(get ready to press ctrl-C quick, or else run it on an OS that
can deal with an out of memory situation without crashing)
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:

Formerly PR gcj/292

>Unformatted: