8328822: C2: "negative trip count?" assert failure in profile predicate code

[shipilev]

Simple corner case fix in C2.

Additional testing:

• New regression test fails without the fix, passes with it

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8328822 needs maintainer approval

Issue

• JDK-8328822: C2: "negative trip count?" assert failure in profile predicate code (Bug - P3 - Approved)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk22u.git pull/179/head:pull/179
$ git checkout pull/179

Update a local copy of the PR:
$ git checkout pull/179
$ git pull https://git.openjdk.org/jdk22u.git pull/179/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 179

View PR using the GUI difftool:
$ git pr show -t 179

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk22u/pull/179.diff

Webrev

Link to Webrev Comment

[shipilev]

/approval request Simple corner case fix in C2. Regression test is sensitive to the bug. The lower than usual risk for C2 changes, as fix is trivial.

[bridgekeeper]

👋 Welcome back shade! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@shipilev 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:

8328822: C2: "negative trip count?" assert failure in profile predicate code

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 4 new commits pushed to the master branch:

• beb06e1: 8330094: RISC-V: Save and restore FRM in the call stub
• 5c15483: 8326201: [S390] Need to bailout cleanly if creation of stubs fails when code cache is out of space
• e96e6ab: 8329850: [AIX] Allow loading of different members of same shared library archive
• d2e1ea4: 8328703: Illegal accesses in Java_jdk_internal_org_jline_terminal_impl_jna_linux_CLibraryImpl_ioctl0

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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 master branch, type /integrate in a new comment.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[openjdk]

⚠️ @shipilev This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

[openjdk]

@shipilev
8328822: The approval request has been created successfully.

[mlbridge]

Webrevs

• 00: Full (b242c2a1)

[shipilev]

/integrate

[openjdk]

Going to push as commit e77a047.
Since your change was applied there have been 4 commits pushed to the master branch:

• beb06e1: 8330094: RISC-V: Save and restore FRM in the call stub
• 5c15483: 8326201: [S390] Need to bailout cleanly if creation of stubs fails when code cache is out of space
• e96e6ab: 8329850: [AIX] Allow loading of different members of same shared library archive
• d2e1ea4: 8328703: Illegal accesses in Java_jdk_internal_org_jline_terminal_impl_jna_linux_CLibraryImpl_ioctl0

Your commit was automatically rebased without conflicts.

[openjdk]

@shipilev Pushed as commit e77a047.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.