8334890: Missing unconditional cross modifying fence in nmethod entry barriers #1131
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The change adds an unconditional memory barrier to guarantee the instruction fetcher observes the correct updated immediate.
Merge conflict caused by minor context difference (added comment in a mainline): fixed manually.
Testing: jtreg tier 1-3 on arm64 and x64.
Update. The backport is controversial: while the functional change is correct and necessary, it introduces a regression in SPECjvm2008: JDK-8337778
Update.
SPECjvm2008-Derby-ZGC performance on linux-aarch64 is not affected with patch applied to jdk21u
Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/1131/head:pull/1131
$ git checkout pull/1131
Update a local copy of the PR:
$ git checkout pull/1131
$ git pull https://git.openjdk.org/jdk21u-dev.git pull/1131/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1131
View PR using the GUI difftool:
$ git pr show -t 1131
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/1131.diff
Using Webrev
Link to Webrev Comment