Mercurial > hg > truffle
comparison src/share/vm/runtime/orderAccess.hpp @ 671:d0994e5bebce
6822204: volatile fences should prefer lock:addl to actual mfence instructions
Reviewed-by: kvn, phh
author | never |
---|---|
date | Thu, 26 Mar 2009 14:31:45 -0700 |
parents | 98cb887364d3 |
children | bd02caa94611 |
comparison
equal
deleted
inserted
replaced
668:90a66aa50514 | 671:d0994e5bebce |
---|---|
298 static void release_store_ptr_fence(volatile void* p, void* v); | 298 static void release_store_ptr_fence(volatile void* p, void* v); |
299 | 299 |
300 // In order to force a memory access, implementations may | 300 // In order to force a memory access, implementations may |
301 // need a volatile externally visible dummy variable. | 301 // need a volatile externally visible dummy variable. |
302 static volatile intptr_t dummy; | 302 static volatile intptr_t dummy; |
303 | |
304 private: | |
305 // This is a helper that invokes the StubRoutines::fence_entry() | |
306 // routine if it exists, It should only be used by platforms that | |
307 // don't another way to do the inline eassembly. | |
308 static void StubRoutines_fence(); | |
303 }; | 309 }; |