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

David Chase david.r.chase at oracle.com
Wed May 22 04:43:20 PDT 2013

I think the idea is that false is safe, therefore it is the default.

On 2013-05-22, at 7:23 AM, David Holmes <david.holmes at oracle.com> wrote:
> Neither of those statements require that the default value of the flag be false. You can have it be true and then verify it is supported - and clear it if not; that all happens before anything would issue the new instructions. If it is not supported and was asked for on the command-line you can detect that too.
> I just find it an odd convention because you can't look at globals.hpp and the command-line and know the value of the flag. But maybe that isn't as common as I think (I tend to mostly look at runtime flags)
> Anyway, moving on ...
> David

More information about the hotspot-compiler-dev mailing list