On Wed, 11 Mar 2026 08:01:59 GMT, Dean Long <[email protected]> wrote:
>> Can't I write bytecode that would invoke monitorexit directly with null on >> the stack? Though I guess we don't really care what happens in that case as >> it is broken bytecode. > > In that case, "monitor matching" that the comment below is talking about > would have failed. But this is all existing behavior that this PR does not > change. So I left this block of code that's indented but I haven't figured out what it means. I probably should have made this a draft PR until then but maybe you can help. The comment in aload_0 makes no sense. No idea why it would return and not be covered in an exception handler. Same with monitor_top. If the bytecode can throw an exception it should fall through to the code below that creates the exception edge. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/30171#discussion_r2917967227
