User account creation filtered due to spam.
Consider turning -findirect-dispatch on by default. It solves some serious problems with compatibility of classes, e.g. adding/removing methods or changing method order.
The obvious drawback is decreased performance. However some studies have shown the impact to be minimal, and -fno-indirect-dispatch can get the old behavior.
Jeff, what's the status of this? Do you have a testcase exhibiting the problematic behavior? Thanks,
still true (-findirect-dispatch is enabled by default) on the mainline (20030724).
>still true (-findirect-dispatch is enabled by default) on the mainline
Waaaait. This bug is that -findirect-dispatch was *off* by default and should
have been *on*. If -findirect-dispatch is enabled by default in the mainline,
then the bug is *fixed*.
Andrew? Could you clarify? Did you get confused about the nature of the bug,
or did you accidentally omit the word 'not'?
I missed the word not. woops.
Closing as won't fix as the Java front-end has been removed from the trunk.