On Tue, 10 Mar 2026 19:09:14 GMT, Coleen Phillimore <[email protected]> wrote:
> Please review this change to fix GenerateOopMap to not report an unreachable
> bytecode for async exception handling and for the first bytecode in an
> exception catch clause. The first change will generate a safepoint entry
> that doesn't allow async exceptions for bytecodes that cannot trap. The
> second change creates an exception edge for the first bytecode in an
> exception catch clause whether it can trap or not.
> This also adds a GenerateOopMapALot at safeopints to test interpreter oopmap
> generation. Tested JCKs with this option.
> Thanks to @tkrodriguez for the kill003 test.
> Also tested tier1-8.
src/hotspot/share/runtime/interfaceSupport.cpp line 70:
> 68: }
> 69: // Verify interpreter oopmap generation
> 70: if (!_no_async && GenerateOopMapALot) {
Based on the description of GenerateOopMapALot, I would expect this to execute
even for the async case.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/30171#discussion_r2915453419
