[concurrency-interest] Runtime intrinsic info

Vladimir Ivanov vladimir.x.ivanov at oracle.com
Sat Oct 31 18:17:18 EDT 2015

The short answer is no.

Intrinsification is not a static property. In HotSpot some methods are 
always intrinsifed and some are not (it depends on runtime conditions 
and call site context). VM can decide on per-call site basis.

In 9 all "intrinsifiable" methods should be marked with 
@HotSpotIntrinsicCandidate [1]. Otherwise, HotSpot complains.

In previous releases, -XX:+PrintInlining shows a message for every 
intrinsified method.

Or, inspect HotSpot sources [2]. All intrinsics JVM knows about are 
listed there.

Best regards,
Vladimir Ivanov



On 10/31/15 11:40 PM, thurstonn wrote:
> Hello,
> Is there some way to verify that some particular method (say in Unsafe) is
> intrinsfied within a JVM at runtime?  Other than viewing the assembly code?
> Something sort of like JOL does for class layout
> Thanks
> --
> View this message in context: http://jsr166-concurrency.10961.n7.nabble.com/Runtime-intrinsic-info-tp12850.html
> Sent from the JSR166 Concurrency mailing list archive at Nabble.com.
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest

More information about the Concurrency-interest mailing list