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

John Rose john.r.rose at oracle.com
Thu May 16 15:16:45 PDT 2013

On May 16, 2013, at 2:56 PM, Christian Thalinger <christian.thalinger at oracle.com> wrote:

> Hmm.  Tao spent a lot of time to move all processor specific flags into the respective globals_<arch>.hpp file.  I don't think we should undo this.

I agree.  That opens the question of how to manage the PUTPROP call in shared code (jvm.cpp).

David, as a least-bad solution, I suggest protecting the x86-specific names in jvm.cpp with X86_ONLY:

+  X86_ONLY(PUTPROP(props, "sun.zip.clmulSupported", UseAVX && UseCLMUL ? "true" : "false"));


+  PUTPROP(props, "sun.zip.clmulSupported", X86_ONLY(UseAVX && UseCLMUL ||) false ? "true" : "false"));


+  PUTPROP(props, "sun.zip.clmulSupported", X86_ONLY(UseAVX && UseCLMUL ? "true" :) "false"));

— John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20130516/6ea47fba/attachment.html 

More information about the hotspot-compiler-dev mailing list