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.
------------- Commit messages: - Add IgnoreUnrecognizedVMOptions - Add a GenerateOopMapALot debugging option for use for testing. - 8074292: nsk/jdb/kill/kill001: generateOopMap.cpp assert(bb->is_reachable()) failed Changes: https://git.openjdk.org/jdk/pull/30171/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=30171&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8074292 Stats: 275 lines in 13 files changed: 226 ins; 12 del; 37 mod Patch: https://git.openjdk.org/jdk/pull/30171.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/30171/head:pull/30171 PR: https://git.openjdk.org/jdk/pull/30171
