8357381: C2: assert(false) failed: should not be here - #32467
8357381: C2: assert(false) failed: should not be here#32467TobiHartmann wants to merge 2 commits into
Conversation
|
/contributor add @sarannat |
|
👋 Welcome back thartmann! A progress list of the required criteria for merging this PR into |
|
@TobiHartmann 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 /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 50 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 |
|
@TobiHartmann |
|
@TobiHartmann 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. |
|
The total number of required reviews for this PR has been set to 2 based on the presence of this label: |
vnkozlov
left a comment
There was a problem hiding this comment.
Looks good. thank you for picking it up.
| igvn->hash_insert(use); | ||
| record_for_optimizer(use); | ||
| --i; | ||
| } else if (use->is_memory_access_intrinsic()) { |
There was a problem hiding this comment.
Is there any reason why a memory_access_intrinsic is handled differently from a MemNode?
There was a problem hiding this comment.
As far as I know, there is no semantic difference. This is basically the "meat" of the original fix proposed in #31037: MemNodes are already processed through the memnode_worklist, while memory-access intrinsics are not MemNodes and do not go through that path. Therefore, when Ideal() exposes a direct memory edge, move_inst_mem() repairs it here.
Unifying the two paths might be cleaner, but would require more invasive changes.
merykitty
left a comment
There was a problem hiding this comment.
Thanks, that sounds reasonable.
|
Thanks Quan-Anh! |
|
/integrate |
|
Going to push as commit a7977b8.
Your commit was automatically rebased without conflicts. |
|
@TobiHartmann Pushed as commit a7977b8. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This is a clone of #31037, finishing the integration for @sarannat.
Incremental changes:
GrowableArraytoUnique_Node_Listfororig_phiswhich was changed in the meantime by JDK-8358560.is_mem_read_only_string_intrinsicby the newis_memory_access_intrinsic.-XX:CompileThreshold=1000and duplicate@runsfrom the test. Added warmup and increased iterations to make it more robust. I also added a run without flags.Thanks,
Tobias
Progress
Issue
Reviewers
Contributors
<snatarajan@openjdk.org>Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/32467/head:pull/32467$ git checkout pull/32467Update a local copy of the PR:
$ git checkout pull/32467$ git pull https://git.openjdk.org/jdk.git pull/32467/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 32467View PR using the GUI difftool:
$ git pr show -t 32467Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/32467.diff
Using Webrev
Link to Webrev Comment