8316181: Move the fast locking implementation out of the .ad files

[rkennke]

Backport of https://git.openjdk.org/jdk/commit/b48dbf6bfa652ef031c35f0a85a409142563aa72, to ease subsequent backport. Unclean because of context diffs, especially related to biased-locking.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed (1 review required, with at least 1 Committer)

Issue

• JDK-8316181: Move the fast locking implementation out of the .ad files (Enhancement - P4)

Reviewers

• Aleksey Shipilev (@shipilev - Committer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/lilliput-jdk17u.git pull/72/head:pull/72
$ git checkout pull/72

Update a local copy of the PR:
$ git checkout pull/72
$ git pull https://git.openjdk.org/lilliput-jdk17u.git pull/72/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 72

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/lilliput-jdk17u/pull/72.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

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

[openjdk]

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

8316181: Move the fast locking implementation out of the .ad files

Reviewed-by: shade

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 no new commits pushed to the lilliput branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the lilliput branch, type /integrate in a new comment.

[mlbridge]

Webrevs

• 00: Full (f8e3224b)

[openjdk]

⚠️ @rkennke could not find any commit with hash c0a2ef4d6521aa5c0c18a78c1cd8e20dda382fed. Please update the title with the hash for an existing commit.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[shipilev]

Looks fine, assuming it was a mechanical move that does not change the code any substantially beyond dropping __ -> everywhere.

[rkennke]

Looks fine, assuming it was a mechanical move that does not change the code any substantially beyond dropping __ -> everywhere.

Yep, that's exactly how I did it. Thanks!

/integrate

[openjdk]

Going to push as commit 263af2e.

[openjdk]

@rkennke Pushed as commit 263af2e.

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