Make AtomicReferenceFieldUpdater
fields static
for [better performance](https://shipilev.net/blog/2015/faster-atomic-fu/#:~:text=thrown%20out%20of%20the%20window).
#7606
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.
Make
AtomicReferenceFieldUpdater
fieldsstatic
for better performance.This may eliminate the reason for an
Unsafe
-based implementation even under Java 8, but we will ideally confirm that with benchmarks before ripping that implementation out. (There's also Android:AtomicReferenceFieldUpdater
is available there, but we should look into performance, including under older versions, especially with AFAIK no plans to removeUnsafe
there.)(Also, make a few other tiny edits to the backport copy so that it matches the mainline copy more closely.)
RELNOTES=n/a