JDK-6975121 : OrderAccess should use compiler intrinsics where possible
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 7,8
  • Priority: P4
  • Status: Closed
  • Resolution: Won't Fix
  • OS: generic
  • CPU: generic
  • Submitted: 2010-08-06
  • Updated: 2017-12-04
  • Resolved: 2017-12-04
Related Reports
Relates :  
JDK-8061964 - Insufficient compiler barriers for GCC in OrderAccess functions
Relates :  
JDK-6973570 - OrderAccess::storestore() scales poorly on multi-socket x64 and sparc: cache-line ping-ponging
Description
Starting with SS12.2, our compilers will support compiler intrinsics for barriers
implemented now in OrderAccess. In some cases, we may be able to simplify our
implementations, make them more portable and perhaps more performant by simply using
the compiler-provided intrinsics
Comments
Specific platforms are adding order access and atomic intrinsics when needed. This is not on our list of current priorities. If there are additional specific customer requirements, we will consider reopening this issue. Closing as WNF.
04-12-2017
This is an Enhancement request not a bug.
09-02-2017
Rickard Backman has been looking at additional compiler intrinsic optimizations - for gcc as well.
13-03-2013
This covers both compiler barriers: http://www.oracle.com/technetwork/server-storage/solarisstudio/documentation/oss-compiler-barriers-176055.pdf and hardware barriers: http://www.oracle.com/technetwork/server-storage/solarisstudio/documentation/oss-memory-barriers-fences-176056.pdf The SunStudio docs are here: http://docs.oracle.com/cd/E18659_01/html/821-1383/gjzmf.html
21-12-2012