RFR: 8225716: G1 GC: Undefined behaviour in G1BlockOffsetTablePart::block_at_or_preceding

[Aleksey Shipilev]

On 6/17/19 2:37 PM, Andrew Haley wrote:
> http://cr.openjdk.java.net/~aph/8225716-jdk8u/
> 
> This patch had to be backported with changes because current Atomic
> support doesn't work for byte accesses, so volatile will suffice.

Well, there are OrderAccess j(u)byte methods you can use here, along with some STATIC_ASSERTs that
verify uchar and jubyte actually agree? Or even explicit fences before/after the access to get
acquire/release?

It would be awkward to have the same bug ID having different memory semantics fixes.

-Aleksey