-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8348261: assert(n->is_Mem()) failed: memory node required #23938
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
Conversation
👋 Welcome back kvn! A progress list of the required criteria for merging this PR into |
@vnkozlov 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 2 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 ➡️ To integrate this PR with the above commit message to the |
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 to me!
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 reasonable.
Is there maybe some kind of stress-flag we could develop? Because you are saying the reproduction depends on some specific probabilities.
} else if (n->Opcode() == Op_StrCompressedCopy || | ||
n->Opcode() == Op_EncodeISOArray) { | ||
// get the memory projection | ||
n = n->find_out_with(Op_SCMemProj); | ||
assert(n != nullptr && n->Opcode() == Op_SCMemProj, "memory projection required"); | ||
} else { | ||
#ifdef ASSERT | ||
if (!n->is_Mem()) { |
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 turn this into a product check? Could we bail-out gracefully at this point?
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.
For first question - may be but we hit it first time since JDK 9. I think we should balance what is really needs to be checked in product and what can be done in debug VM. For this case I think checking in debug is fine.
For second question - not from EA but we can from compilation. We are in split_unique_types()
where we start modifying graph already.
Thank you, Christian and Emanuel for reviews |
I think stressing flag |
My testing tier1-5, xcomp and stress passed without new failures. |
/integrate |
Going to push as commit f6a8db2.
Your commit was automatically rebased without conflicts. |
Add missing check for StrInflatedCopy intrinsic in C2 Escape Analysis.
Very rare case since we not usually use Latin1.inflate(). In failing case we inline both paths in String.getBytes() and eliminate `TreeMap$EntryIterator allocation:
Unfortunately I was not able to create standalone test - it seems requires very particular frequencies of executed paths and used features/flags. The fix was verified with compilation replay file from the bug report.
I am running testing and will let you know results.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23938/head:pull/23938
$ git checkout pull/23938
Update a local copy of the PR:
$ git checkout pull/23938
$ git pull https://git.openjdk.org/jdk.git pull/23938/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23938
View PR using the GUI difftool:
$ git pr show -t 23938
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23938.diff
Using Webrev
Link to Webrev Comment