Compiled call version seems to be slower

[Ulf Zibis]

Am 26.11.2009 09:27, Christian Thalinger schrieb:
> On Thu, 2009-11-26 at 00:12 +0100, Ulf Zibis wrote:
>   
>>
>>>> Additionally I'm wondering why the finally block is copy-and-pasted
>>>> for 
>>>> each separate return.
>>>> Is that as disired ?
>>>>         

Sorry about asking once more. Would it be so hard to avoid the 6-times 
redundancy of the finally block, or are there other reasons?


>> Additional question:
>> What does that mean in exact, that there are 2 little different
>> compiler outputs for the same method?
>> Which of the 2 would actually run?
>>     
>
> Ahh, sorry, I misunderstood.  The two disassemblies are from the same
> run, I thought these are two different runs.
>
> Well, the first version seem to have been invalidated, for whatever
> reason, and got recompiled.  A -XX:+PrintCompilation would probably tell
> us.  And it's very likely that a second compile is different than the
> first one (more profiling data, different inlining, ...).
>   

Much thanks, so my worry about, that the "slower" one would come to 
account, is obsolete.

-Ulf