Line number support for interpreter

Mark Wielaard mark@klomp.org
Thu May 20 06:05:00 GMT 2004


Hi,

On Wed, 2004-05-19 at 21:34, Bryce McKinlay wrote:
> Mark Wielaard wrote:
> 
> >It might be a good idea to add this small test to testsuite/libjava.lang
> >since it seems a strange corner case that isn't normally tested/used.
> 
> The libjava.lang/InvokeInterface.java test should cover this case 
> already. Does that test not fail for you?

Nope. And I finally found out why. InvokeInterface was compiled by
gcj -C but my test program by jikes (1.18). And when InvokeInterface is
compiled with jikes then it fails also when run with gij!

What was happening was that jikes cleverly makes sure that the interface
is never initialized. While gcj -C just gets us a initialized class when
using the I.class construct.

The attached Test program does the same. And does fail with gij (CVS),
but not with gij 3.4 (which wrongly initializes the interface I when the
array is created). I'll add something like this to Mauve since I saw
that more runtimes get this wrong.

Cheers,

Mark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Invoke.java
Type: text/x-java
Size: 767 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/java-patches/attachments/20040520/0c0a28b4/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://gcc.gnu.org/pipermail/java-patches/attachments/20040520/0c0a28b4/attachment.sig>


More information about the Java-patches mailing list