Tests if the synchronized section provides the essential barriers
JVM options: [-XX:TieredStopAtLevel=1] Iterations: 5 Time: 200
| Observed state | Occurrence | Expectation | Interpretation |
|---|---|---|---|
| 0, 0 | 1697170 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 100057 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 0 | ACCEPTABLE_INTERESTING | The write to $b is observed, but write to $a is not. This is the counter-intuitive behavior,but the coding pattern is incorrect: alone "sync" barrier is not enough to get the properacquire/release semantics. |
| 1, 2 | 159483 | ACCEPTABLE | The write to $b is observed, expected to see $a == 1. |
JVM options: [-server] Iterations: 5 Time: 200
| Observed state | Occurrence | Expectation | Interpretation |
|---|---|---|---|
| 0, 0 | 238063 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 12217 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 45 | ACCEPTABLE_INTERESTING | The write to $b is observed, but write to $a is not. This is the counter-intuitive behavior,but the coding pattern is incorrect: alone "sync" barrier is not enough to get the properacquire/release semantics. |
| 1, 2 | 4546065 | ACCEPTABLE | The write to $b is observed, expected to see $a == 1. |
JVM options: [-client] Iterations: 5 Time: 200
| Observed state | Occurrence | Expectation | Interpretation |
|---|---|---|---|
| 0, 0 | 148226 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 10988 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 84 | ACCEPTABLE_INTERESTING | The write to $b is observed, but write to $a is not. This is the counter-intuitive behavior,but the coding pattern is incorrect: alone "sync" barrier is not enough to get the properacquire/release semantics. |
| 1, 2 | 2272112 | ACCEPTABLE | The write to $b is observed, expected to see $a == 1. |
JVM options: [-server, -XX:-TieredCompilation, -XX:+UnlockDiagnosticVMOptions, -XX:+StressLCM, -XX:+StressGCM] Iterations: 5 Time: 200
| Observed state | Occurrence | Expectation | Interpretation |
|---|---|---|---|
| 0, 0 | 523418 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 9224 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 1197 | ACCEPTABLE_INTERESTING | The write to $b is observed, but write to $a is not. This is the counter-intuitive behavior,but the coding pattern is incorrect: alone "sync" barrier is not enough to get the properacquire/release semantics. |
| 1, 2 | 1470721 | ACCEPTABLE | The write to $b is observed, expected to see $a == 1. |
JVM options: [-server, -XX:-TieredCompilation] Iterations: 5 Time: 200
| Observed state | Occurrence | Expectation | Interpretation |
|---|---|---|---|
| 0, 0 | 154551 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 1269 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 267 | ACCEPTABLE_INTERESTING | The write to $b is observed, but write to $a is not. This is the counter-intuitive behavior,but the coding pattern is incorrect: alone "sync" barrier is not enough to get the properacquire/release semantics. |
| 1, 2 | 3851433 | ACCEPTABLE | The write to $b is observed, expected to see $a == 1. |
JVM options: [-Xint] Iterations: 5 Time: 200
| Observed state | Occurrence | Expectation | Interpretation |
|---|---|---|---|
| 0, 0 | 51868 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 1475 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 0 | ACCEPTABLE_INTERESTING | The write to $b is observed, but write to $a is not. This is the counter-intuitive behavior,but the coding pattern is incorrect: alone "sync" barrier is not enough to get the properacquire/release semantics. |
| 1, 2 | 85057 | ACCEPTABLE | The write to $b is observed, expected to see $a == 1. |
JVM options: [-client, -XX:-TieredCompilation] Iterations: 5 Time: 200
| Observed state | Occurrence | Expectation | Interpretation |
|---|---|---|---|
| 0, 0 | 208364 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 1250 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 249 | ACCEPTABLE_INTERESTING | The write to $b is observed, but write to $a is not. This is the counter-intuitive behavior,but the coding pattern is incorrect: alone "sync" barrier is not enough to get the properacquire/release semantics. |
| 1, 2 | 1931037 | ACCEPTABLE | The write to $b is observed, expected to see $a == 1. |
JVM options: [-server, -XX:+UnlockDiagnosticVMOptions, -XX:+StressLCM, -XX:+StressGCM] Iterations: 5 Time: 200
| Observed state | Occurrence | Expectation | Interpretation |
|---|---|---|---|
| 0, 0 | 42747 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 1592 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 38 | ACCEPTABLE_INTERESTING | The write to $b is observed, but write to $a is not. This is the counter-intuitive behavior,but the coding pattern is incorrect: alone "sync" barrier is not enough to get the properacquire/release semantics. |
| 1, 2 | 848673 | ACCEPTABLE | The write to $b is observed, expected to see $a == 1. |