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

Aleksey Shipilev aleksey.shipilev at oracle.com
Fri May 10 13:48:02 PDT 2013

On 05/11/2013 12:44 AM, Aleksey Shipilev wrote:
> But by far the better option seems to invert control: expose the
> PCLMULQDQ-compatible method on Java side, and then intrinsify it in
> compiler, like we do with AES. See vmSymbols.hpp and library_call.cpp,
> search for "_aescrypt_encryptBlock".

Or, if you still need the flag, follow the suit of AtomicLong with


More information about the hotspot-compiler-dev mailing list