8295414: [Aarch64] C2: assert(false) failed: bad AD file

[zhengxiaolinX]

This is a fix for a fast debug build assertion failure, and the impact is small.
Clean backport from 20.

Testing hotspot tier1~tier4.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8295414: [Aarch64] C2: assert(false) failed: bad AD file

Reviewers

• Tobias Hartmann (@TobiHartmann - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 78

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk19u/pull/78.diff

[bridgekeeper]

👋 Welcome back xlinzheng! 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]

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

[openjdk]

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

8295414: [Aarch64] C2: assert(false) failed: bad AD file

Reviewed-by: thartmann

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@TobiHartmann) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[mlbridge]

Webrevs

• 00: Full (f3a33788)

[TobiHartmann]

Looks good.

[zhengxiaolinX]

Thank you, Tobias! (I saw another backport there which was closed :-) )

Hotspot tier1 and tier2 look okay and I received approval to push.

/integrate

[openjdk]

@zhengxiaolinX
Your change (at version f3a3378) is now ready to be sponsored by a Committer.

[RealFYang]

/sponsor

[openjdk]

Going to push as commit 2adc3e1.

[openjdk]

@RealFYang @zhengxiaolinX Pushed as commit 2adc3e1.

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