-
Notifications
You must be signed in to change notification settings - Fork 208
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
8303466: C2: failed: malformed control flow. Limit type made precise with MaxL/MinL #2635
Conversation
👋 Welcome back mbalao! A progress list of the required criteria for merging this PR into |
@martinuy 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 16 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 |
This backport pull request has now been updated with issue from the original commit. |
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.
That looks good to me.
|
The GHA macos-aarch64 failure at build time seems unrelated to this backport. |
/approval request jdk17u is affected by this bug and would benefit from its fix. The patch does not apply cleanly but has been reviewed. |
/integrate |
Going to push as commit 445aba4.
Your commit was automatically rebased without conflicts. |
Hi,
I would like to propose a backport of 8303466 [1] to jdk17u. jdk17u can benefit from this fix and having more accurate limit type information.
The JDK main line patch (introduced for JDK 21) does not apply cleanly because of the following:
src/hotspot/share/opto/convertnode.cpp
src/hotspot/share/opto/loopTransform.cpp
The CastIINode node inserted during the first unrolling to keep precise type information after inserting an Opaque2 node is still needed, but has to be inserted before the node is used for ConvI2LNode -> SubLNode -> MaxLNode/MinLNode -> ... Otherwise, bottom type propagates accross this nodes path. The type of the node has to reflect the original limit type. MaxLNode/MinLNode will handle the clamping effect over the type.
In addition to the previous conflicts, the following changes were applied:
No regressions observed in hotspot:tier1.
Thanks,
Martin.-
--
[1] - https://bugs.openjdk.org/browse/JDK-8303466
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/2635/head:pull/2635
$ git checkout pull/2635
Update a local copy of the PR:
$ git checkout pull/2635
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/2635/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 2635
View PR using the GUI difftool:
$ git pr show -t 2635
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/2635.diff
Webrev
Link to Webrev Comment