Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JDK-8310020: MacroAssembler::call_VM(_leaf) doesn't consistently check for conflict with C calling convention. #14470

Closed
wants to merge 3 commits into from

Conversation

dafedafe
Copy link
Contributor

@dafedafe dafedafe commented Jun 14, 2023

Issue

The MacroAssembler::call_VM and MacroAssembler::call_VM_leaf methods don't include asserts to check if the passed arguments collide with the C calling convention registers consistently. Some versions omit them completely (e.g. aarch64 MacroAssembler::call_VM_leaf), other ones use regular asserts (where the assert_different_registers function should be used).

Solution

We use assert_different_registers across all MacroAssembler::call_VM and MacroAssembler::call_VM_leaf where a check is needed (except for the arm implementation, which doesn't change as it uses fixed registers).

Testing

This fix includes changes for x86_32/64 and aarch64, which I could test thoroughly but also for ppc, riscv, and s390 for which I would need some help with testing.


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-8310020: MacroAssembler::call_VM(_leaf) doesn't consistently check for conflict with C calling convention. (Enhancement - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 14470

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

Using diff file

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

Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Jun 14, 2023

👋 Welcome back dafedafe! 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 Jun 14, 2023

@dafedafe 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 Jun 14, 2023
@dafedafe dafedafe changed the title JDK-8310020: MacroAssembler::call_VM_leaf doesn't consistently check for conflict with C calling convention. JDK-8310020: MacroAssembler::call_VM(_leaf) doesn't consistently check for conflict with C calling convention. Jun 14, 2023
@dafedafe dafedafe marked this pull request as ready for review June 15, 2023 06:50
@openjdk openjdk bot added the rfr Pull request is ready for review label Jun 15, 2023
@mlbridge
Copy link

mlbridge bot commented Jun 15, 2023

Webrevs

Co-authored-by: Tobias Hartmann <tobias.hartmann@oracle.com>
Copy link
Member

@TobiHartmann TobiHartmann left a comment

Choose a reason for hiding this comment

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

Looks good to me.

@openjdk
Copy link

openjdk bot commented Jun 15, 2023

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

8310020: MacroAssembler::call_VM(_leaf) doesn't consistently check for conflict with C calling convention.

Reviewed-by: thartmann, fyang, mdoerr, amitkumar

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

  • 79069c5: 8310314: Misplaced "unnamed classes are a preview feature and are disabled by default" error
  • 96a7db7: 8309228: Clarify EXPERIMENTAL flags comment in hotspot/share/runtime/globals.hpp
  • b2e86ae: 8304478: Initial nroff manpage generation for JDK 22
  • 7b45c8f: 8241800: Disable IPV6_MULTICAST_ALL to prevent interference from all multicast groups
  • 137a5f7: 8310105: LoongArch64 builds are broken after JDK-8304913
  • 33c6ec9: 8310019: MIPS builds are broken after JDK-8304913
  • e08e94f: 8310266: JFR: Refactor after 'view' command
  • f8f8bfb: 8309939: HttpClient should not use Instant.now() as Instant source for deadlines
  • 7d4b77a: 8304835: jdk/jfr/event/oldobject/TestArrayInformation.java fails with "Could not find event with class ... as (leak) object"
  • b896e3e: 8310146: Removing unused PerfLongVariant::_sampled
  • ... and 54 more: https://git.openjdk.org/jdk/compare/4c18b9e1faba32bd54a5d8b0b3c21b07f694c71b...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 (@TobiHartmann, @RealFYang, @TheRealMDoerr, @offamitkumar) 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 ready Pull request is ready to be integrated label Jun 15, 2023
@RealFYang
Copy link
Member

RealFYang commented Jun 15, 2023

Hello, I can help do some tests on linux-riscv64 platform.
But I think we need following extra changes for riscv. Could you please help add this? Thanks.

diff --git a/src/hotspot/cpu/riscv/macroAssembler_riscv.cpp b/src/hotspot/cpu/riscv/macroAssembler_riscv.cpp
index e6d1e66e0c0..32a144b2d42 100644
--- a/src/hotspot/cpu/riscv/macroAssembler_riscv.cpp
+++ b/src/hotspot/cpu/riscv/macroAssembler_riscv.cpp
@@ -666,6 +666,7 @@ void MacroAssembler::call_VM_leaf(address entry_point, Register arg_0) {
 }

 void MacroAssembler::call_VM_leaf(address entry_point, Register arg_0, Register arg_1) {
+  assert_different_registers(arg_1, c_rarg0);
   pass_arg0(this, arg_0);
   pass_arg1(this, arg_1);
   call_VM_leaf_base(entry_point, 2);
@@ -673,6 +674,8 @@ void MacroAssembler::call_VM_leaf(address entry_point, Register arg_0, Register

 void MacroAssembler::call_VM_leaf(address entry_point, Register arg_0,
                                   Register arg_1, Register arg_2) {
+  assert_different_registers(arg_1, c_rarg0);
+  assert_different_registers(arg_2, c_rarg0, c_rarg1);
   pass_arg0(this, arg_0);
   pass_arg1(this, arg_1);
   pass_arg2(this, arg_2);

@dafedafe
Copy link
Contributor Author

Thanks @RealFYang, I missed it! It should be fixed now.
Thanks for testing too!

Copy link
Member

@RealFYang RealFYang left a comment

Choose a reason for hiding this comment

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

Updated change LGTM. I can do native fastdebug build with this and run non-trivial benchmark workloads on linux-riscv64 platform. Thanks.

@dafedafe
Copy link
Contributor Author

This PR includes changes for ppc and s390 that I couldn't test either.
@TheRealMDoerr, @offamitkumar could I ask you if you could please run some tests on this change as well for ppc/s390 (and possibly also have a quick look at it)? Thank you very much!

Copy link
Contributor

@TheRealMDoerr TheRealMDoerr left a comment

Choose a reason for hiding this comment

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

Thanks for cleaning this up! PPC64 part is good.

Copy link
Member

@offamitkumar offamitkumar left a comment

Choose a reason for hiding this comment

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

LGTM, Test result also came clean. A few other assert-occurrence could be updated but I guess those are out of scope for this PR.

Thank you very much for the change :-)

@dafedafe
Copy link
Contributor Author

@TobiHartmann @offamitkumar @TheRealMDoerr @RealFYang thank you very much for your reviews!

@dafedafe
Copy link
Contributor Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Jun 20, 2023
@openjdk
Copy link

openjdk bot commented Jun 20, 2023

@dafedafe
Your change (at version a7a1abd) is now ready to be sponsored by a Committer.

@offamitkumar
Copy link
Member

/sponsor

@openjdk
Copy link

openjdk bot commented Jun 20, 2023

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

  • 79069c5: 8310314: Misplaced "unnamed classes are a preview feature and are disabled by default" error
  • 96a7db7: 8309228: Clarify EXPERIMENTAL flags comment in hotspot/share/runtime/globals.hpp
  • b2e86ae: 8304478: Initial nroff manpage generation for JDK 22
  • 7b45c8f: 8241800: Disable IPV6_MULTICAST_ALL to prevent interference from all multicast groups
  • 137a5f7: 8310105: LoongArch64 builds are broken after JDK-8304913
  • 33c6ec9: 8310019: MIPS builds are broken after JDK-8304913
  • e08e94f: 8310266: JFR: Refactor after 'view' command
  • f8f8bfb: 8309939: HttpClient should not use Instant.now() as Instant source for deadlines
  • 7d4b77a: 8304835: jdk/jfr/event/oldobject/TestArrayInformation.java fails with "Could not find event with class ... as (leak) object"
  • b896e3e: 8310146: Removing unused PerfLongVariant::_sampled
  • ... and 54 more: https://git.openjdk.org/jdk/compare/4c18b9e1faba32bd54a5d8b0b3c21b07f694c71b...master

Your commit was automatically rebased without conflicts.

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

openjdk bot commented Jun 20, 2023

@offamitkumar @dafedafe Pushed as commit 0878872.

💡 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.

5 participants