> If there are two threads calling `Executable.hasRealParameterData()` under > race and the first one writes into volatile `Executable.parameters` field > (doing _releasing store_) and the second thread reads non-null value from the > same field (doing acquiring read) then it must read exactly the same value > written into `hasRealParameterData` within `privateGetParameters()`. The > reason for this is that we assign `hasRealParameterData` before _releasing > store_. > > In the opposite case (_acquiring read_ reads null) the second thread writes > the value itself and returns it from the method so there is no change in > behavior.
Сергей Цыпанов has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains four additional commits since the last revision: - Merge branch 'master' into 8288327 - 8288327: Use record store - 8288327: Add clarifying comments - 8288327: Executable.hasRealParameterData should not be volatile ------------- Changes: - all: https://git.openjdk.org/jdk/pull/9143/files - new: https://git.openjdk.org/jdk/pull/9143/files/5c52be9f..076cde01 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=9143&range=02 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=9143&range=01-02 Stats: 9459 lines in 287 files changed: 5494 ins; 2884 del; 1081 mod Patch: https://git.openjdk.org/jdk/pull/9143.diff Fetch: git fetch https://git.openjdk.org/jdk pull/9143/head:pull/9143 PR: https://git.openjdk.org/jdk/pull/9143
