Re: Monkey wrench for compiling JDK 1.2 class files

["Jonathan P. Olson" <olson at mmsi dot com>]

On Wed, 22 Sep 1999, Anthony Green wrote:
>Hi Jon -
>
>> jikesos (from IBM) just generates plain terrible code with dead byte
>> code everywhere about which gcj bitterly complains.
>
>What do you mean exactly by `complains'?  The compiler issues warnings
>for dead code.  It used to be the it would fail completely.  Jikes
>would, for instance, generate exception regions that ended in dead
>code.  Gcj can handle this now, so all you should be seeing are
>warning messages.
>
>Maybe the warning messages should be optional.
>
>Are you still using an old compiler?
>
>AG
>

True, it only issues warning messages, but so many warning messages
are bothersome to read through when building a large system with lots
of class files.  Plus, the quality of the generated native code is highly
dependent on the quality of the byte code that gcj starts with.  It's quite
important to start with good byte code to finsh with a decent native
code module.

>-- 
>Anthony Green                                               Cygnus Solutions
>                                                       Sunnyvale, California
--
Jon Olson, Modular Mining Systems
	   3289 E. Hemisphere Loop
	   Tucson, AZ 85706
olson@mmsi.com
Phone:	(520)746-9127
Fax:	(520)889-5790