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

[Christian Thalinger]

On May 16, 2013, at 3:16 PM, John Rose <john.r.rose at oracle.com> wrote:

> 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:

A better way would be to call an architecture specific method which adds all the required properties.  Since this is only a temporary solution maybe we shouldn't go there and the #ifdef is fine.

-- Chris

> 
> +  X86_ONLY(PUTPROP(props, "sun.zip.clmulSupported", UseAVX && UseCLMUL ? "true" : "false"));
> 
> or:
> 
> +  PUTPROP(props, "sun.zip.clmulSupported", X86_ONLY(UseAVX && UseCLMUL ||) false ? "true" : "false"));
> 
> or:
> 
> +  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/e395f164/attachment.html