> 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. ------------- Changes: - all: https://git.openjdk.org/jdk/pull/30171/files - new: https://git.openjdk.org/jdk/pull/30171/files/c2ce4272..143842d8 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=30171&range=07 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=30171&range=06-07 Stats: 28 lines in 2 files changed: 0 ins; 27 del; 1 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
