JDK-4894843 : RFE: switch from eager deoptimization to lazy deoptimization
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.4.2_06,5.0
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,linux
  • CPU: generic,x86
  • Submitted: 2003-07-23
  • Updated: 2012-10-13
  • Resolved: 2003-08-12
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.
Other
5.0 tigerFixed
Related Reports
Duplicate :  
Relates :  
Description
Hotspot current eagerly deoptimizes nmethods. This reuires it to carry a lot
of state around in vframeArrays and more importantly requires it to patch
return addresses in frames. Patching return addresses in frames is one reason
why the jni trampoline was needed on register window machines. If we switch
to lazy deopt then with a small amount of work in the interpreter we can eliminate the jni trampoline (which is added overhead on all jni calls) and
greatly reduce the complexity of stack walking (no more deoptimized frames)
and simplify the deopt code by making vframeArray handling much simpler.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b16 tiger-b20 tiger-b21 tiger-b22
14-06-2004

EVALUATION Description says it all. ###@###.### 2003-07-23
23-07-2003