RFR: 7143664: Clean up OrderAccess implementations and usage
david.holmes at oracle.com
Tue Feb 10 01:37:45 UTC 2015
On 10/02/2015 5:22 AM, Dean Long wrote:
> On 2/8/2015 11:14 PM, David Holmes wrote:
>> In OrderAccess::fence doesn't the existing asm already act as a
>> compiler barrier; and on uniprocessor we need neither compiler nor
>> hardware barriers; so isn't the compiler_barrier() redundant?
> Wouldn't a uniprocessor need compiler barriers just in case it got a
> context switch in the middle of compiler-reordered instructions?
Yes of course you are right.
More information about the hotspot-dev