On Wed, 18 Mar 2026 17:54: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. > > Coleen Phillimore has updated the pull request with a new target base due to > a merge or a rebase. The pull request now contains eight commits: > > - Merge branch 'master' into kill001 > - GenerateOopMapALot at all safepoints even ones that cannot throw async > exceptions. > - Add some comments and fix the test. > - Update test/hotspot/jtreg/vmTestbase/nsk/jdb/kill/kill003/kill003a.java > > Co-authored-by: Joel Sikström <[email protected]> > - Sort includes. > - Add IgnoreUnrecognizedVMOptions > - Add a GenerateOopMapALot debugging option for use for testing. > - 8074292: nsk/jdb/kill/kill001: generateOopMap.cpp > assert(bb->is_reachable()) failed It does seem like we would need a no_async version of _breakpoint(). ------------- PR Comment: https://git.openjdk.org/jdk/pull/30171#issuecomment-4086342346
