JDK-8173795 : AOT support in raw_exception_handler_for_return_address is broken
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • CPU: generic
  • Submitted: 2017-02-01
  • Updated: 2019-09-13
  • Resolved: 2017-04-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 10
10 b21Fixed
Related Reports
Blocks :  
JDK-8173699 - Crash during deoptimization with "assert(result == __null || result->is_oop()) failed: must be oop"
Relates :  
JDK-8173019 - Backout JDK-8172990 changes.
Description
The problem reported by 8173019 is still there.
Comments
great, thanks for checking.
21-02-2017
Yes, the crash went away. That's why I targeted this for 10.
21-02-2017
[~dlong], have you checked if the crash goes away after JDK-8173699 has been pushed?
21-02-2017
ILW = Inefficient exception handling, with AOT code, no workaround = MMH = P3
15-02-2017
There are two problems here. The first is the same as 8173699, when we go through the unpack_with_exception_in_tls path. The other problem is an AOT problem, because we fail to take the unpack_with_exception path in SharedRuntime::raw_exception_handler_for_return_address. This bug is for the latter AOT problem. If 8173699 is fixed, then the crash will go away, so this fix is not crucial for 9. I have targeted it for 10.
02-02-2017