JDK-7131259 : compile_method and CompilationPolicy::event shouldn't be declared TRAPS
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: hs23
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: solaris_10
- CPU: x86
- Submitted: 2012-01-18
- Updated: 2012-03-24
- Resolved: 2012-03-24
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.
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 7 | JDK 8 | Other |
|---|---|---|
7u4Fixed  |
8Fixed |
hs23Fixed |
Related Reports
|
Relates :
|
Description
In this particular case we're throwing an OOM while inside the counter overflow on entry to a method. The exception appears to propagate up from compile_method, presumably from the resolve_string_constants and load_signature_classes calls. compile_method_base is also declared TRAPS though it can't actually throw an exception. I think the whole path from CompilationPolicy::event to compile_method_base should be cleaned up so that exceptions can't propagate. Any exception thrown in the path are side effects and not exception that should even be propagated to the regular Java code. I'll file a separate bug for this.
Comments
|