-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Conversation
👋 Welcome back aph! A progress list of the required criteria for merging this PR into |
@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:
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
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 |
@theRealAph 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. |
Webrevs
|
There was a problem hiding this 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);
It's a safety in depth patch.
Yes, it should. |
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. |
There was a problem hiding this 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 |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
/integrate |
Going to push as commit 5a0bdd0.
Your commit was automatically rebased without conflicts. |
@theRealAph Pushed as commit 5a0bdd0. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
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
Issue
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