Skip to content

Conversation

@cnqpzhang
Copy link
Contributor

@cnqpzhang cnqpzhang commented Mar 4, 2025

According to tests on Arm CPUs Neoverse-N1/N2/V1/V2 and Ampere-Altra/AmpereOne, -XX:+UseSignumIntrinsic can provide consistent positive performance boost on singnum microbenchmarks (1-4,5,7 in below list) and no obvious regression (ops/s change <0.1%) on other relevant tests (6,9-12). In addition, "Apple M1 shows no regression with signum intrinsics" (verified by @theRealAph). So, it can be the time to enable this UseSignumIntrinsic flag by default for aarch64-port. By the way, x86 and riscv ports have already configured it on by default.

Tests: passed JTReg tier1 tests on Ampere-1A, no regression found, and particularly checked test results of two signum cases (13,14), both are in good state.

1. org.openjdk.bench.java.lang.MathBench.signumDouble
2. org.openjdk.bench.java.lang.MathBench.signumFloat
3. org.openjdk.bench.java.lang.StrictMathBench.sigNumDouble
4. org.openjdk.bench.java.lang.StrictMathBench.signumFloat
5. org.openjdk.bench.vm.compiler.Signum._1_signumFloatTest
6. org.openjdk.bench.vm.compiler.Signum._2_overheadFloat
7. org.openjdk.bench.vm.compiler.Signum._3_signumDoubleTest
8. org.openjdk.bench.vm.compiler.Signum._4_overheadDouble
9. org.openjdk.bench.vm.compiler.Signum._5_copySignFloatTest
10. org.openjdk.bench.vm.compiler.Signum._6_overheadCopySignFloat
11. org.openjdk.bench.vm.compiler.Signum._7_copySignDoubleTest
12. org.openjdk.bench.vm.compiler.Signum._8_overheadCopySignDouble
13. JTReg: compiler/vectorization/TestSignumVector.java
14. JTReg: compiler/intrinsics/math/TestSignumIntrinsic.java


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-8350663: AArch64: Enable UseSignumIntrinsic by default (Enhancement - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 23893

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

Using diff file

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

Using Webrev

Link to Webrev Comment

Signed-off-by: Patrick Zhang <patrick@os.amperecomputing.com>
@bridgekeeper
Copy link

bridgekeeper bot commented Mar 4, 2025

👋 Welcome back qpzhang! 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
Copy link

openjdk bot commented Mar 4, 2025

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

8350663: AArch64: Enable UseSignumIntrinsic by default

Reviewed-by: adinn

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

  • a37d843: 8352015: LIBVERIFY_OPTIMIZATION remove special optimization settings
  • b891bfa: 8352022: RISC-V: Support Zfa fminm_h/fmaxm_h for float16
  • 20f1bca: 8351187: Add JFR monitor notification event
  • 46b3d1d: 8351382: New test containers/docker/TestMemoryWithSubgroups.java is failing
  • 558c015: 8351921: G1: Pinned regions with pinned objects only reachable by native code crash VM
  • f8c2122: 8352138: G1: Remove G1AddMetaspaceDependency.java test
  • e1bcff3: 8345687: Improve the implementation of SegmentFactories::allocateSegment
  • f4ddac5: 8331201: UBSAN enabled build reports on Linux x86_64 runtime error: shift exponent 65 is too large for 64-bit type 'long unsigned int'
  • 38499b3: 8352084: Add more test code in TestSetupAOT.java
  • 19154f7: 8351970: Retire JavaLangAccess::exit
  • ... and 167 more: https://git.openjdk.org/jdk/compare/1f10ffba88119caab169b1fc43ccfd143e3b85a6...master

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 (@adinn) 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).

@openjdk openjdk bot added the rfr Pull request is ready for review label Mar 4, 2025
@openjdk
Copy link

openjdk bot commented Mar 4, 2025

@cnqpzhang 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.

@openjdk openjdk bot added the hotspot hotspot-dev@openjdk.org label Mar 4, 2025
@mlbridge
Copy link

mlbridge bot commented Mar 4, 2025

Webrevs

@cnqpzhang
Copy link
Contributor Author

Hi @theRealAph Could you please help review this? Thanks.

Copy link
Contributor

@adinn adinn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change is good.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Mar 18, 2025
@cnqpzhang
Copy link
Contributor Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Mar 18, 2025
@openjdk
Copy link

openjdk bot commented Mar 18, 2025

@cnqpzhang
Your change (at version 2e012df) is now ready to be sponsored by a Committer.

@adinn
Copy link
Contributor

adinn commented Mar 18, 2025

/sponsor

@openjdk
Copy link

openjdk bot commented Mar 18, 2025

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

  • a37d843: 8352015: LIBVERIFY_OPTIMIZATION remove special optimization settings
  • b891bfa: 8352022: RISC-V: Support Zfa fminm_h/fmaxm_h for float16
  • 20f1bca: 8351187: Add JFR monitor notification event
  • 46b3d1d: 8351382: New test containers/docker/TestMemoryWithSubgroups.java is failing
  • 558c015: 8351921: G1: Pinned regions with pinned objects only reachable by native code crash VM
  • f8c2122: 8352138: G1: Remove G1AddMetaspaceDependency.java test
  • e1bcff3: 8345687: Improve the implementation of SegmentFactories::allocateSegment
  • f4ddac5: 8331201: UBSAN enabled build reports on Linux x86_64 runtime error: shift exponent 65 is too large for 64-bit type 'long unsigned int'
  • 38499b3: 8352084: Add more test code in TestSetupAOT.java
  • 19154f7: 8351970: Retire JavaLangAccess::exit
  • ... and 167 more: https://git.openjdk.org/jdk/compare/1f10ffba88119caab169b1fc43ccfd143e3b85a6...master

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Mar 18, 2025
@openjdk openjdk bot closed this Mar 18, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Mar 18, 2025
@openjdk
Copy link

openjdk bot commented Mar 18, 2025

@adinn @cnqpzhang Pushed as commit b025d8c.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hotspot hotspot-dev@openjdk.org integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

2 participants