JDK-6968367 : can_post_on_exceptions is still using VM_DeoptimizeFrame in some places
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: hs19
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_9
  • CPU: sparc
  • Submitted: 2010-07-12
  • Updated: 2011-04-23
  • Resolved: 2011-04-23
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 6 JDK 7 Other
6u25Fixed 7Fixed hs20Fixed
Related Reports
Relates :  
JDK-6902182 - Starting with jdwp agent should not incur performance penalty
Description
The fix for 6902182 to speed up running with an agent missed a few places where C1 was using the VM_DeoptimizeFrame and those should be updated.
Comments
EVALUATION http://hg.openjdk.java.net/jdk7/build/hotspot/rev/ce6848d0666d
04-12-2010
EVALUATION 6968367: can_post_on_exceptions is still using VM_DeoptimizeFrame in some places Reviewed-by: kvn, twisti The fix for 6902182 changed some call sites where deopt is needed to call directly into deoptimize_frame instead of using VM_DeoptimizeFrame but it missed quite a few places, particularly in the client compiler. Instead of directly modifying each site to use the appropriate version I modified Deoptimization::deoptimize_frame to select the appropriate version, made VM_DeoptimizeFrame private, and updated all call sites to use the main entry point. Tested with all the nsk JVMTI tests.
21-10-2010