On Wed, 25 Mar 2026 20:32:30 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. > > Coleen Phillimore has updated the pull request incrementally with one > additional commit since the last revision: > > Allow async exceptions on returns and have GOM create an exception edge if > the bytecode is covered by a handler in the method. @JornVernee should I problem list this FFM test for this PR to unblock it? ------------- PR Comment: https://git.openjdk.org/jdk/pull/30171#issuecomment-4201641243
