RFR (S) : 8014362 : Need to expose some processor features via Unsafe interface

David Chase david.r.chase at oracle.com
Fri May 10 14:52:46 PDT 2013

On 2013-05-10, at 5:36 PM, Aleksey Shipilev <aleksey.shipilev at oracle.com> wrote:
> Aha. Ok, so the flag then. I would say go through the JNI like
> AtomicLong does to catch that flag without contaminating the Unsafe
> without a good reason.

I don't understand.  Merely going through JNI is not enough -- the implementation has to be within hotspot, because that's where the flag is.  java.util.zip.CRC32 already goes through JNI, but it is does not see hotspot symbols (I know, because I tried that first).

And what should I be contaminating, if not Unsafe?


More information about the hotspot-compiler-dev mailing list