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

8346890: AArch64: Type profile counters generate suboptimal code #23012

Closed
wants to merge 4 commits into from

Conversation

theRealAph
Copy link
Contributor

@theRealAph theRealAph commented Jan 9, 2025

Type profile counters are emitted many times in C1-generated code. The generator was written a long time ago before we knew how best to write AArch64 code, and the generated code is rather suboptimal.

This PR reduces the size of a typical bimorphic type profile counter from 33 to 27 instructions.


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-8346890: AArch64: Type profile counters generate suboptimal code (Enhancement - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 23012

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Jan 9, 2025

👋 Welcome back aph! 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 Jan 9, 2025

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

8346890: AArch64: Type profile counters generate suboptimal code

Reviewed-by: shade, 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 313 new commits pushed to the master branch:

  • 4a375e5: 8344232: [PPC64] secondary_super_cache does not scale well: C1 and interpreter
  • 0df9dcb: 8346572: Check is_reserved() before using ReservedSpace instances
  • a09f06d: 8348265: RMIConnectionImpl: Remove Subject.callAs on MarshalledObject
  • 0395593: 8346751: Internal java compiler error with type annotations in constants expression in constant fields
  • 2daafe4: 8348283: java.lang.classfile.components.snippets.PackageSnippets shipped in java.base.jmod
  • 50ca450: 8340784: Remove PassFailJFrame constructor with screenshots
  • 416d469: 8347008: beancontext package spec does not clearly explain why the API is deprecated
  • 471d63c: 8343609: Broken links in java.xml
  • 7f16a08: 8348240: Remove SystemDictionaryShared::lookup_super_for_unregistered_class()
  • 48ece07: 8282862: AwtWindow::SetIconData leaks old icon handles if an exception is detected
  • ... and 303 more: https://git.openjdk.org/jdk/compare/bd0fde71d9113bad902e71b61f0ca44c650809ef...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.

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

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

openjdk bot commented Jan 9, 2025

@theRealAph 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 Jan 9, 2025
@mlbridge
Copy link

mlbridge bot commented Jan 9, 2025

Webrevs

Copy link
Member

@shipilev shipilev left a comment

Choose a reason for hiding this comment

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

Can you explain a bit more here? I think I get why would we want to rewrite lea+ldr to slot_at.

I do not quite understand why do we rewrite this one:

-    Address data_addr(mdo, md->byte_offset_of_slot(data, ReceiverTypeData::receiver_count_offset(i)));
-    __ addptr(data_addr, DataLayout::counter_increment);
+    __ addptr(slot_at(ReceiverTypeData::receiver_count_offset(i)),
+              DataLayout::counter_increment);

Does it really optimize anything to rewrite it to slot_at? If so, shouldn't this one in the other hunk also get rewritten?

         Address data_addr(mdo, md->byte_offset_of_slot(data, VirtualCallData::receiver_count_offset(i)));
          __ addptr(data_addr, DataLayout::counter_increment);

@theRealAph
Copy link
Contributor Author

Can you explain a bit more here? I think I get why would we want to rewrite lea+ldr to slot_at.

I do not quite understand why do we rewrite this one:

-    Address data_addr(mdo, md->byte_offset_of_slot(data, ReceiverTypeData::receiver_count_offset(i)));
-    __ addptr(data_addr, DataLayout::counter_increment);
+    __ addptr(slot_at(ReceiverTypeData::receiver_count_offset(i)),
+              DataLayout::counter_increment);

Does it really optimize anything to rewrite it to slot_at? If so, shouldn't this one in the other hunk also get rewritten?

It's a safety in depth patch.
It's good practice always to check variable offsets in order to ensure that they are reachable. addptr has an embedded form_address, so this is not strictly necessary. It is, however, harmless.

         Address data_addr(mdo, md->byte_offset_of_slot(data, VirtualCallData::receiver_count_offset(i)));
          __ addptr(data_addr, DataLayout::counter_increment);

Yes, it should.

@theRealAph
Copy link
Contributor Author

For clarity: every variable-sized load/store offset generated by C1 should be range-checked, and when it is out of range the load/store should be split. We already do this in C2. I'll wrap up any missing examples in a later patch.

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.

Changes look good apart from a nit over the comment

@@ -1173,6 +1173,7 @@ class MacroAssembler: public Assembler {

// Arithmetics

// Clobber: rscratch2
Copy link
Contributor

@adinn adinn Jan 23, 2025

Choose a reason for hiding this comment

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

I'm not entirely sure why this has been added as part of this fix. It's ok as a comment but 1) I'm not sure why you do not also note that addptr also clobbers rscratch1 and 2) cmpptr clobbers rscratch1 but not rscratch2 but it is not clear that this comment only applies to addptr. Perhaps a newline between the two methods would make that clearer.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed.
As to why the comment change is part of this particular fix, I always put a little flag over a pothole when I see one.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jan 23, 2025
@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Jan 23, 2025
@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jan 24, 2025
@theRealAph
Copy link
Contributor Author

/integrate

@openjdk
Copy link

openjdk bot commented Jan 24, 2025

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

  • 4a375e5: 8344232: [PPC64] secondary_super_cache does not scale well: C1 and interpreter
  • 0df9dcb: 8346572: Check is_reserved() before using ReservedSpace instances
  • a09f06d: 8348265: RMIConnectionImpl: Remove Subject.callAs on MarshalledObject
  • 0395593: 8346751: Internal java compiler error with type annotations in constants expression in constant fields
  • 2daafe4: 8348283: java.lang.classfile.components.snippets.PackageSnippets shipped in java.base.jmod
  • 50ca450: 8340784: Remove PassFailJFrame constructor with screenshots
  • 416d469: 8347008: beancontext package spec does not clearly explain why the API is deprecated
  • 471d63c: 8343609: Broken links in java.xml
  • 7f16a08: 8348240: Remove SystemDictionaryShared::lookup_super_for_unregistered_class()
  • 48ece07: 8282862: AwtWindow::SetIconData leaks old icon handles if an exception is detected
  • ... and 303 more: https://git.openjdk.org/jdk/compare/bd0fde71d9113bad902e71b61f0ca44c650809ef...master

Your commit was automatically rebased without conflicts.

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

openjdk bot commented Jan 24, 2025

@theRealAph Pushed as commit 5a0bdd0.

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

3 participants