1
100%
master: 100%

Ran 03 Jul 2021 10:50PM UTC

Files 73

Run time 5s

Badge

Embed ▾

Committed 03 Jul 2021 09:44PM UTC coverage: 92.561% (+0.05%) from 92.516%

Job # #2607.1

Build Type

push

github-actions

Committed by

ben-manes

Commit Message

Stronger memory-order for when setting a value

The plain write to the value piggybacked on the volatile fence when the
lock is released for guaranteed visibility. However, we should not
assume that visibility delayed until this fence, as the underlying
system may inject a fence earlier (e.g. safepont, context switch). As
the compiler may change program order for plain reads and writes, those
cases must ensure that there is are no dependencies for partial
visibility. While true for strong values, the change in 37c51d5  shows a
dependency order is needed for weak/soft values. For stricter
correctness, clearing the Reference must occur after the entry's value
has been visibly changed. Therefore, the release/acquire ordering is
used to ensure we abide by the Java Memory Model, rather than on x86's
total store order (TSO).

For more details, see
http://gee.cs.oswego.edu/dl/html/j9mm.html

Coverage Stats

6209 of 6708 relevant lines covered (92.56%)

0.93 hits per line

ben-manes / caffeine / #2607 / 1
100%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job #2607.1

ben-manes / caffeine / #2607 / 1 100% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job #2607.1

ben-manes / caffeine / #2607 / 1
100%
master: 100%

README BADGES
x