On Wed, 25 Oct 2023 10:10:57 GMT, Jorn Vernee <jver...@openjdk.org> wrote:
>> Explicitly handle UpcallStub allocation failures by terminating. We >> currently might try to use the returned `nullptr` which would fail sooner or >> later. This patch just makes the termination explicit. > > Jorn Vernee has updated the pull request incrementally with one additional > commit since the last revision: > > call fatal without holding code cache lock I agree that avoiding a VM fatal error is preferable, like a recent [change](https://github.com/openjdk/jdk/pull/15970) to make JVMCI RuntimeStub creation failure result in a BailoutException instead of a fatal error. ------------- PR Comment: https://git.openjdk.org/jdk/pull/16311#issuecomment-1781254062
