8388882: Disable automatic integer spills to floating point registers on Intel platforms#32031
8388882: Disable automatic integer spills to floating point registers on Intel platforms#32031missa-prime wants to merge 1 commit into
Conversation
|
👋 Welcome back missa! A progress list of the required criteria for merging this PR into |
|
@missa-prime 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: 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 20 new commits pushed to the
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 (@sviswa7, @dwhite-intel) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
@missa-prime The following label will be automatically applied to this pull request:
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. |
|
The total number of required reviews for this PR has been set to 2 based on the presence of this label: |
|
/label hotspot-compiler |
|
@sviswa7 |
When operating on integer variables using supported Intel CPUs, the current approach is to spill onto floating point registers when general purpose registers aren't available. Unfortunately, it appears that the cost of doing this is higher than just leaving those variables on the stack. This change disables the
UseFPUForSpillingflag by default on Intel CPUs.To measure performance, the
SpillCode.testSpillForManyIntsmicro-benchmark was run on the parts listed below.The table below shows how performance changed using the OpenJDK v28-b6 build. The Baseline column represents runs where the flag was enabled, and the New columns represents runs where the flag was disabled. Each result is the mean of 4 individual runs. Overall, setting
UseFPUForSpillingto false provides an uplift between 7% and 10%.Additionally, other micro-benchmarks show improvements when disabling the flag.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/32031/head:pull/32031$ git checkout pull/32031Update a local copy of the PR:
$ git checkout pull/32031$ git pull https://git.openjdk.org/jdk.git pull/32031/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 32031View PR using the GUI difftool:
$ git pr show -t 32031Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/32031.diff
Using Webrev
Link to Webrev Comment