-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8367014: Rename class Atomic to AtomicAccess #27135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
👋 Welcome back kbarrett! A progress list of the required criteria for merging this PR into |
|
@kimbarrett This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 3 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
|
@kimbarrett The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks for taking this on!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AtomicAccess is a bit wordy, and this change is going to mess up diffs for backports terribly, but I can't think of a better way to do it. Thanks.
There was a bunch of internal to Oracle bike shedding over the names already. But I'm open to more if someone Diffs for backports are going to get messed up anyway, since most uses of |
Sure, I imagine there was! It's a shame when decision making happens behind closed doors in a FOSS project, but public list bikeshedding would have been too much for this change.
That's fair. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've checked through the patch and it looks good. I found one file that lacked alignment adjustments.
Although the file "atomic.hpp" is being renamed to "atomicAccess.hpp", I chose
to not rename the various "atomic_." and "atomic__." files.
Could you motivate why you chose to not do that?
| template<> | ||
| template<typename D, typename I> | ||
| inline D Atomic::PlatformAdd<4>::fetch_then_add(D volatile* dest, I add_value, | ||
| inline D AtomicAccess::PlatformAdd<4>::fetch_then_add(D volatile* dest, I add_value, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file has multiple alignment issues.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, completely missed that file. Will fix.
|
@kimbarrett this pull request can not be integrated into git checkout atomic-access
git fetch https://git.openjdk.org/jdk.git master
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge master"
git push |
I thought about it, and waffled back and forth. But I was trying to do as much |
|
Updated for recent commits adding some new uses of |
Speaking as an archaeologist and the lead of multiple backport projects, I agree with you, Kim. |
Sure, renames are annoying. I do think that it is bad to leave inconsistent names in a long-lived, evolving code base. |
| return -4 * (4 + slow_path_size(nm)); | ||
| case NMethodPatchingType::conc_instruction_and_data_patch: | ||
| return -4 * (10 + slow_path_size(nm)); | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This and similar changes for arm and riscv came from a merged changeset.
I took that new version and updated it for Atomic:: => AtomicAccess:: renaming.
| return nullptr; | ||
| } | ||
| return jt; | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another case of taking a merge update and then adjusting for Atomic:: => AtomicAccess::.
|
|
||
| #include "runtime/objectMonitor.inline.hpp" | ||
|
|
||
| inline markWord BasicLock::displaced_header() const { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These functions were removed by a merge update.
|
Needs re-review because of updates to deal with merge conflicts and to update newly merged code that needed |
|
Hm, now says there is a new merge conflict. Guess you folks should hold off on re-review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still good. Thanks
|
Thanks for reviews @theRealAph , @stefank , and @dholmes-ora |
|
/integrate |
|
Going to push as commit 9e843f5.
Your commit was automatically rebased without conflicts. |
|
@kimbarrett Pushed as commit 9e843f5. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this change that renames the all-static class
AtomictoAtomicAccess. The reason for this name change is to allow the introductionof the new type
Atomic<T>(JDK-8367013).The PR has several commits, according to the specific category of change being
made. It may be easier to review the PR by studying these individual commits.
Although the file "atomic.hpp" is being renamed to "atomicAccess.hpp", I chose
to not rename the various "atomic_." and "atomic__." files.
There are a number of comments containing the word "Atomic" that I didn't
change. They are generically about atomic operations, and will just as well
serve as referring to the future
Atomic<T>.Testing: mach5 tier1, GHA sanity tests.
This is one of those changes where successful builds indicate the change is good.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27135/head:pull/27135$ git checkout pull/27135Update a local copy of the PR:
$ git checkout pull/27135$ git pull https://git.openjdk.org/jdk.git pull/27135/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27135View PR using the GUI difftool:
$ git pr show -t 27135Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27135.diff
Using Webrev
Link to Webrev Comment