Any::isNull check

[Vitaly Davidovich]

One caveat here; if you don't eliminate dead code before JIT sees the
method, it may be too big for inlining and suffer performance loss.

On Wednesday, December 16, 2015, Brian Goetz <brian.goetz at oracle.com> wrote:

> HotSpot is *really* good at eliminating dead code based on type profiles.
>
> On 12/16/2015 10:38 AM, Paul Benedict wrote:
>
>> When a method is specialized for values, Any::isNull can only return
>> "false", which means if(Any.isNull(o)) can only ever have one outcome --
>> the other code branch can be discarded by the compiler. I know it's too
>> early to talk about optimizations :-) but will javac be smart enough to
>> recognize this optimization? Is it on your list for the future?
>>
>> Cheers,
>> Paul
>>
>
>

-- 
Sent from my phone