Tests if the synchronized section provides the essential barriers
JVM options: [-server] Iterations: 5 Time: 200
| Observed state | Occurrence | Expectation | Interpretation |
|---|---|---|---|
| 0, 0 | 110866 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 6486 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 281 | 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 | 931557 | ACCEPTABLE | The write to $b is observed, expected to see $a == 1. |
JVM options: [-XX:TieredStopAtLevel=1] Iterations: 5 Time: 200
| Observed state | Occurrence | Expectation | Interpretation |
|---|---|---|---|
| 0, 0 | 1941648 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 93723 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 274 | 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 | 165695 | 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 | 1323267 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 101814 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 209 | 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 | 118490 | 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 | 12454 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 1307 | 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 | 29379 | 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 | 801878 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 64940 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 1082 | 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 | 181190 | 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 | 105542 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 4573 | 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 | 145 | 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 | 731338 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 75638 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 1801 | 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 | 309063 | 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 | 1056609 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 51424 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 285 | 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 | 249472 | ACCEPTABLE | The write to $b is observed, expected to see $a == 1. |