> 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 five 
additional commits since the last revision:

 - Fix copyrights and extraneous diffs
 - Add a bit of logging for GenerateOopMapALot.
 - Restored special aload, return, monitorexit cases in do_exception_edge. Make 
them exceptions from async exception delivery instead.
 - Remove monitorenter, monitorexit from do_exception_edge since they can have 
exceptions, and turn off GenerateOopMapALot again.
 - Generate safepoint checks with and without allowing async exceptions a 
different way.  Also include the breakpoint code.

-------------

Changes:
  - all: https://git.openjdk.org/jdk/pull/30171/files
  - new: https://git.openjdk.org/jdk/pull/30171/files/232acba3..de495dc3

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=30171&range=05
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=30171&range=04-05

  Stats: 97 lines in 10 files changed: 54 ins; 23 del; 20 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

Reply via email to