-
Notifications
You must be signed in to change notification settings - Fork 720
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
Update BCDCHK uncommoning for off-heap #20302
base: master
Are you sure you want to change the base?
Conversation
Personal build without off-heap changes to verify that I am not missing any dependencies. Internal issue tracking the failure. Context into the failure:
[1] compare/off-heap...VermaSh:openj9:off-heap_daa_failure?expand=1 "Fix patch" |
e5e230d
to
8e4f933
Compare
Update BCDCHK uncommoning for off-heap because address node of BCDCHK can be aloadi with single child if off-heap is enabled. Signed-off-by: Shubham Verma <[email protected]>
8e4f933
to
c934487
Compare
Relaunched personal build without off-heap changes because previous had a lot of infra related failures. |
@@ -62,17 +62,44 @@ UncommonBCDCHKAddressNode::perform() | |||
{ | |||
TR::Node* pdOpNode = node->getFirstChild(); | |||
TR::Node* oldAddressNode = node->getSecondChild(); | |||
TR_ASSERT(pdOpNode && oldAddressNode, "Unexpected null PD opNode or address node under BCDCHK"); | |||
TR_ASSERT(oldAddressNode->getNumChildren() == 2, "Expecting 2 children under address node of BCDCHK."); | |||
TR_ASSERT_FATAL_WITH_NODE(node, pdOpNode && oldAddressNode, "Unexpected null PD opNode or address node under BCDCHK"); |
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 understand that this is the old code, but if the intention of this assert is that both oldAddressNode
and pdOpNode
should be non null, then we should explicitly check that.
|
||
TR::ILOpCodes addressOp = oldAddressNode->getOpCodeValue(); | ||
TR_ASSERT((addressOp == TR::aladd || addressOp == TR::aiadd), "Unexpected addressNode opcode"); | ||
TR_ASSERT_FATAL_WITH_NODE(node, |
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.
Would it make sense to have the expected tree structure comment moved here before the ASSERT to highlight what you are checking here?
TR::Node* newAddressNode = NULL; | ||
if (oldAddressNode->getOpCodeValue() == TR::aloadi) | ||
{ | ||
/* Expected tree structure (probably just loading first array element because offset is 0) |
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 elaborate why probably?
Update BCDCHK uncommoning for off-heap because address node of BCDCHK can be aloadi with single child if off-heap is enabled.