Tests if the synchronized section provides the essential barriers
JVM options: [-server, -XX:-TieredCompilation, -XX:+UnlockDiagnosticVMOptions, -XX:+StressLCM, -XX:+StressGCM] Iterations: 5 Time: 200
| Observed state | Occurrence | Expectation | Interpretation |
|---|---|---|---|
| 0, 0 | 159940 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 2993 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 33 | 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 | 2158724 | 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 | 533510 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 26432 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 1730 | 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 | 4369528 | 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 | 45142 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 1550 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 44 | 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 | 4199034 | 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 | 118216 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 850 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 7 | 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 | 2682927 | 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 | 98449 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 205 | 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 | 36856 | 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 | 546165 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 541 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 5 | 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 | 622459 | 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 | 166589 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 87 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 5 | 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 | 989799 | 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 | 30518 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 0, 2 | 567 | ACCEPTABLE | The write to $b is not visible yet; we can observe whatever in $a. |
| 1, 0 | 1924 | 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 | 966021 | ACCEPTABLE | The write to $b is observed, expected to see $a == 1. |