8218145: block_if_requested is not proper inlined due to size

[dchuyko]

This small optimization through a trivial refactoring is applicable to 11u. Original patch requires adjustment in a single place: there is initialize_serialize_page() in safepointMechanism.hpp because JDK-8213436 is not backported.

Testing: tier1, tier2.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8218145: block_if_requested is not proper inlined due to size

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk11u-dev pull/102/head:pull/102
$ git checkout pull/102

Update a local copy of the PR:
$ git checkout pull/102
$ git pull https://git.openjdk.java.net/jdk11u-dev pull/102/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 102

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk11u-dev/pull/102.diff

[bridgekeeper]

👋 Welcome back dchuyko! 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]

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

[openjdk]

@dchuyko This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

8218145: block_if_requested is not proper inlined due to size

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 4 new commits pushed to the master branch:

• 02c0cf6: 8267424: CTW: C1 fails with "State must not be null"
• bdf8568: 8250588: Shenandoah: LRB needs to save/restore fp registers for runtime call
• 1d204c5: 8260589: Crash in JfrTraceIdLoadBarrier::load(_jclass*)
• c1deb0c: 8213922: fix ctw stand-alone build

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.

➡️ 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).

[mlbridge]

Webrevs

• 00: Full (8ff1f5b1)

[dchuyko]

/integrate

[openjdk]

@dchuyko
Your change (at version 8ff1f5b) is now ready to be sponsored by a Committer.

[AlexanderScherbatiy]

/sponsor

[openjdk]

Going to push as commit 2beb7e7.
Since your change was applied there have been 4 commits pushed to the master branch:

• 02c0cf6: 8267424: CTW: C1 fails with "State must not be null"
• bdf8568: 8250588: Shenandoah: LRB needs to save/restore fp registers for runtime call
• 1d204c5: 8260589: Crash in JfrTraceIdLoadBarrier::load(_jclass*)
• c1deb0c: 8213922: fix ctw stand-alone build

Your commit was automatically rebased without conflicts.

[openjdk]

@AlexanderScherbatiy @dchuyko Pushed as commit 2beb7e7.

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