Re: gcj producing bad code

[Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>]

Per Bothner wrote:

> The getY() isn't a super invocation - it's the same as
>   (super.getX()).getY()
> or even:
>   X t = super.getX();
>   return t.getY();
>
> If we're emitting invokespecial to call getY, then I don't think
> the flaw in actually in the bytecode-generation, but more likely
> the front-end (resolve_qualified_expression_name in parse.y)
> incorrectly setting CALL_WITH_SUPER. 


Yes, there is definately a problem here. super.getX().getY() produces a 
different result to x = super.getX(); x.getY(). We need to fix this for 3.1.

regards

Bryce.