[jdk25u] RFR: 8359064: Expose reason for marking nmethod non-entrant to JVMCI client

[duke]

On Thu, 23 Oct 2025 07:32:10 GMT, Cesar Soares Lucas <cslucas at openjdk.org> wrote:

> Hi all, this pull request contains:
> 
> - A backport of commit [2fe12984](https://github.com/openjdk/jdk/commit/2fe12984474656a08c4525c04a351d85be73f658) from the [openjdk/jdk](https://git.openjdk.org/jdk) repository - related to ticket [JDK-8359064](https://bugs.openjdk.org/browse/JDK-8359064). This commit was authored by Cesar Soares on 19 Jun 2025 and was reviewed by Doug Simon and Tom Rodriguez.
> - A cherry-pick of commit [ff54a649](https://github.com/openjdk/jdk/commit/ff54a6493a63cfbcaab7ec90c7db0135e98a7f0c) from the [openjdk/jdk](https://git.openjdk.org/jdk) repository - related to ticket [JDK-8360049](https://bugs.openjdk.org/browse/JDK-8360049). This commit was authored by Doug Simon on 20 Jun 2025 and was reviewed by Andrew Haley and Aleksey Shipilev.
> 
> These changes updates JVMCI interface to receive/send to the external compiler the reason why a nmethod is being invalidated, which will let that compiler make better decisions about future recompilations of the method. Twelve of the files touched in this PR are just hit by collateral effect due to enum type/entries renaming. The remaining of the changes are in the JVMCI interface itself, which shouldn't affect HotSpot in anyway if not running with JVMCI enabled. A few changes are in tests.
> 
> Note that commit `ff54a64` was added to this PR to address a bug on the original patch. These original changes have been integrated in JDK mainline over 5 months ago. Besides GHA the current patch was also tested on my internal CI.
> 
> Thanks!

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

-------------

PR Comment: https://git.openjdk.org/jdk25u/pull/335#issuecomment-3610840917