This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gcj producing bad code

From: Nic Ferrier <nferrier at tapsellferrier dot co dot uk>
To: Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>
Cc: java at gcc dot gnu dot org
Date: 06 Apr 2002 15:31:09 +0100
Subject: Re: gcj producing bad code
References: <87d6xddb12.fsf@pooh-sticks-bridge.tapsellferrier.co.uk><3CAE5E37.20206@waitaki.otago.ac.nz>

Bryce McKinlay <bryce@waitaki.otago.ac.nz> writes:

> It would be very good to have a bug report in GNATS, expecially if you  
> can come up with a test case. Unfortunately, the source->bytecode  
> compilation is probably the buggiest part of GCJ at present. 

I thought it would be tricky to replicate the problem (the Paperclips
code is quite complex at this point) but in fact the problem is quite
simple to define.

GCJ is not compiling method calls quite right... it seems that all
super invocations are done through invokespecial. invokespecial
cannot be used when the target needs to be called through virtual
dispatch however.

I've submitted a bug with some example code. I'm sorry I don't have
the time to commit to fixing it myself.

Nic

Follow-Ups:
- Re: gcj producing bad code
  - From: Eric Blake

References:
- gcj producing bad code
  - From: Nic Ferrier
- Re: gcj producing bad code
  - From: Bryce McKinlay

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]