7414: Avoid volatile writes from Atomics default values

[dreis2211]

Hi,

this PR changes calls like new AtomicInteger(0) to new AtomicInteger() in order to avoid volatile writes.

This would need a ticket in the bug tracker and I hope you can create this for me. OCA should be signed already, but let me know if I need to confirm something again.

In case you think this is worthwhile, I would appreciate it if this is sponsored.

Cheers,
Christoph

---

Progress

• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JMC-7414: Avoid volatile writes from Atomics default values

Reviewers

• Marcus Hirt (@thegreystone - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jmc pull/315/head:pull/315
$ git checkout pull/315

Update a local copy of the PR:
$ git checkout pull/315
$ git pull https://git.openjdk.java.net/jmc pull/315/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 315

View PR using the GUI difftool:
$ git pr show -t 315

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jmc/pull/315.diff

[bridgekeeper]

👋 Welcome back dreis2211! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@dreis2211 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:

7414: Avoid volatile writes from Atomics default values

Reviewed-by: hirt

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 1 new commit pushed to the master branch:

• 085a4a6: 7413: Fix building JMC with Docker

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@thegreystone) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[dreis2211]

/integrate

[openjdk]

@dreis2211
Your change (at version f904809) is now ready to be sponsored by a Committer.

[thegreystone]

/sponsor

[openjdk]

Going to push as commit 14b8357.
Since your change was applied there has been 1 commit pushed to the master branch:

• 085a4a6: 7413: Fix building JMC with Docker

Your commit was automatically rebased without conflicts.

[openjdk]

@thegreystone @dreis2211 Pushed as commit 14b8357.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

[mlbridge]

Webrevs

• 00: Full (f904809e)