why a typeguard single implementation interface field

Aleksey Shipilev shade at redhat.com
Mon Jan 30 10:01:45 UTC 2017


On 01/30/2017 10:50 AM, Peter Veentjer wrote:
> This code shows there is a typeguard; even though there is only a single
> implementation of the 'Service' interface. Why is this typeguard required? If a
> second conflicting implementation of Service would be loaded, why not rely on
> CHA to take care of deoptimizing the code?

Short answer: CHA is not handling interfaces well.

See:
 https://bugs.openjdk.java.net/browse/JDK-6986483
 https://bugs.openjdk.java.net/browse/JDK-8065760

Thanks,
-Aleksey

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20170130/d8a7a258/signature.asc>


More information about the hotspot-compiler-dev mailing list