8293245: x86_64: Extract Adler32 stub implementation into stubGenerator_x86_64_adler.cpp

[iwanowww]

Extract Adler32 stub implementation into a dedicated file (stubGenerator_x86_64_adler.cpp).

Minor cleanups:

• got rid of updateBytesAdler32() by manually inlining it into generate_updateBytesAdler32()
• unified usage of r14 as a scratch register
• added 32-byte alignment for the constants

Testing: hs-tier1 - hs-tier4

---

Progress

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

Issue

• JDK-8293245: x86_64: Extract Adler32 stub implementation into stubGenerator_x86_64_adler.cpp

Reviewers

• Vladimir Kozlov (@vnkozlov - Reviewer) ⚠️ Review applies to 69e427b3
• Dean Long (@dean-long - Reviewer) ⚠️ Review applies to 69e427b3

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10126/head:pull/10126
$ git checkout pull/10126

Update a local copy of the PR:
$ git checkout pull/10126
$ git pull https://git.openjdk.org/jdk pull/10126/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 10126

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10126.diff

[bridgekeeper]

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

[openjdk]

@iwanowww The following label will be automatically applied to this pull request:

• hotspot

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 02: Full (0d5b9f2e)
• 01: Full - Incremental (69e427b3)
• 00: Full (69e427b3)

[vnkozlov]

Good.

[openjdk-notifier]

The dependent pull request has now been integrated, and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork:

git checkout stub.x86_64.adler
git fetch https://git.openjdk.org/jdk master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

[openjdk]

@iwanowww this pull request can not be integrated into master due to one or more merge conflicts. To resolve these merge conflicts and update this pull request you can run the following commands in the local repository for your personal fork:

git checkout stub.x86_64.adler
git fetch https://git.openjdk.org/jdk master
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge master"
git push

[openjdk]

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

8293245: x86_64: Extract Adler32 stub implementation into stubGenerator_x86_64_adler.cpp

Reviewed-by: kvn, dlong

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:

• e1e6732: 8293319: [C2 cleanup] Remove unused other_path arg in Parse::adjust_map_after_if

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.

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

[iwanowww]

Thanks for the review, Vladimir and Dean.

/integrate

[openjdk]

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

• da59618: 8264744: (fs) Use file cloning in Linux version of Files::copy method
• 85d4b49: 8283929: GHA: Add RISC-V build config
• 98d85e6: 8292579: (tz) Update Timezone Data to 2022c
• 7c96608: 8293403: JfrResolution::on_jvmci_resolution crashes when caller is null
• c05015b: 8291736: find_method_handle_intrinsic leaks Method*
• b2067e6: 8291725: Leftover marks when VM shutdown aborts bitmap clearing make mixed gc fail
• 6a1e98c: 8293213: G1: Remove redundant assertion in G1RemSet::clean_card_before_refine
• a92c1ff: 8287912: GTK L&F : Background of tree icons are red
• 272745b: 8293340: Remove unused _code in {Zero,Template}InterpreterGenerator
• 26f2a97: 8290561: Coalesce incubator-module warnings for single-file source-code programs
• ... and 26 more: https://git.openjdk.org/jdk/compare/5757e2129ef23f6aa11a9a29d77ae86971b401c0...master

Your commit was automatically rebased without conflicts.

[openjdk]

@iwanowww Pushed as commit fb6eb6f.

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