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
8256757: Incorrect MachCallRuntimeNode::ret_addr_offset() for CallLeafNoFP on x86_32 #1452
8256757: Incorrect MachCallRuntimeNode::ret_addr_offset() for CallLeafNoFP on x86_32 #1452
Conversation
|
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.
Looks good.
And thanks for fixing it.
How about replacing '5' with 'NativeCall::instruction_size' and also keeping the code generation order like this:
return pre_call_resets_size() + (_leaf_no_fp ? 0 : sizeof_FFree_Float_Stack_All) + NativeCall::instruction_size;
New style follows what is done for |
Okay, I see. Thanks. |
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.
Okay.
@shipilev This change now passes all automated pre-integration checks. 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 7 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the
|
/integrate |
@shipilev Since your change was applied there have been 8 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 9a468d8. |
Importance: fixes one of
tier1
tests, including the runs in GH Actions.JDK-8254231 added new assert in
output.cpp
:Which verifies that the offset returned by MachCallNode::ret_addr_offset() (and sub-types) at matches the emitted code, to avoid potential conflicts between oop maps of different calls.
It caught the failure running
compiler/intrinsics/string/TestStringLatin1IndexOfChar.java
on Linux x86_32. I think that happened because the test forced lower SSE settings. But more tests fail if you force with lower SSE settings with e.g.TEST_VM_OPTS=-XX:UseSSE=1
. The real issue isMachCallRuntimeNode::ret_addr_offset()
computing the offset incorrectly forCallLeafNoFP
: the match rule for it does not includeFFree_Float_Stack_All
. WithUseSSE < 2
,FFree_Float_Stack_All
becomes non-zero.See the definitions in
x86_32.ad
:This does not affect
x86_64
, AFAICS.Additional testing:
tier1
tier1
with-XX:UseSSE=1
Progress
Testing
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/1452/head:pull/1452
$ git checkout pull/1452