This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libgcj/6554: Java cni bug finding class$
- From: tromey at gcc dot gnu dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, inacio at wayne dot spinnakernet dot com, java-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, tromey at gcc dot gnu dot org
- Date: 12 May 2002 01:17:48 -0000
- Subject: Re: libgcj/6554: Java cni bug finding class$
- Reply-to: tromey at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, inacio at wayne dot spinnakernet dot com, java-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, tromey at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
Synopsis: Java cni bug finding class$
Responsible-Changed-From-To: unassigned->tromey
Responsible-Changed-By: tromey
Responsible-Changed-When: Sat May 11 18:17:47 2002
Responsible-Changed-Why:
I'm handling this.
State-Changed-From-To: open->closed
State-Changed-By: tromey
State-Changed-When: Sat May 11 18:17:47 2002
State-Changed-Why:
This isn't actually a bug.
The problem here is that you can't allocate a Java array
using `new'. You must use JvNewObjectArray.
I realize this is an unfriendly restriction, especially
seeing as how it isn't diagnosed by the compiler.
This isn't directly documented, either :-(.
I'll try to write a patch.
There is another PR on this subject. I think that
one mentions our desire to change this. So I am closing
this one as a duplicate.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6554