> 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. > > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai).
Coleen Phillimore has updated the pull request incrementally with two additional commits since the last revision: - Cleanup whitespaces. - Change GenerateOopMap to follow exception edges for all bytecodes during rewriter and interpreter processing, and allow async exceptions to be thrown for any bytecode. ------------- Changes: - all: https://git.openjdk.org/jdk/pull/30171/files - new: https://git.openjdk.org/jdk/pull/30171/files/f175d399..584990f1 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=30171&range=09 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=30171&range=08-09 Stats: 94 lines in 5 files changed: 16 ins; 61 del; 17 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
