8026049: (bf) Intrinsify ByteBuffer.put{Int, Double, Float, ...} methods
David Holmes
david.holmes at oracle.com
Mon Mar 16 11:36:00 UTC 2015
On 16/03/2015 7:29 PM, Andrew Haley wrote:
> On 16/03/15 00:40, David Holmes wrote:
>> Experimental options are supposed to be opt-in only via
>> UnlockExperimentalVMOptions. You presently have the experimental
>> UseUnalignedAccesses being turned on unconditionally on those
>> architectures that support it.
>
> Well, it works. I guess this could be changed to be a product option,
> but it's only really needed for testing. And aren't product options
> supposed to be properly documented for all users?
>
> In other words: please don't say "don't do that." Please tell me what
> I should do instead. All suggestions are welcome, really because I'm
> rather stuck.
Either it should be an experimental option, in which case the logic that
sets the flag on should check that UnlockExperimentalVMOptions is also
on (else do nothing). (Though this would still be a unusual use-case for
an experimental option as the intent is that the user chooses to turn
them on directly.)
Or it should not be an experimental option.
If it is a to be a product flag then it needs to go through the CCC process.
David
-----
> Andrew.
>
More information about the core-libs-dev
mailing list