Jikes Compilation-Optimization Error

[Horst von Brand]

ztang@weber.lcs.mit.edu said:
> If you want to see the .ii file, please contact me (unless someone can
> suggest other alternatives).

You can try to cut it down. For instance, gcc usually tells you with an ICE
where it was compiling. Anything after that function is irrelevant (unless
it happens to be an inline function that is being inlined elsewhere). You
can also delete stuff that isn't being used in the affected function, and
cut that one down to perhaps a few lines. Just check each step that the
problem persists and no new ones appear (other errors, new warnings, ...).
It takes quite a bit of work, but IMHO it is a way in which you can help
the head hackers out, by giving them a more manageable test case.
-- 
Horst von Brand                             vonbrand@sleipnir.valparaiso.cl
Casilla 9G, Viña del Mar, Chile                               +56 32 672616