On 01/22/2016 11:15 AM, Vitaly Davidovich wrote: > I'm guessing opaque is compiler only fence because a method that a > compiler doesn't inline (as an example) is considered "opaque" to > the compiler and serves like a fence. Perhaps that's how opaque > ended up here. At any rate, I think it's a poor name.
Humm. I guess so, but I'm not sure why you'd want a compiler fence in Java. It's not like C where you can access memory-mapped I/O. I suppose it disallows roach-motel code motion. Andrew.