JDK-7071653 : JSR 292: call site change notification should be pushed not pulled
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: hs22
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-07-27
  • Updated: 2011-11-25
  • Resolved: 2011-09-30
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 7 Other
7u2Fixed hs22Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
Description
Currently every speculatively inlined method handle call site has a guard that compares the current target of the CallSite object to the inlined one.  This per-invocation overhead can be removed if the notification is changed from pulled to pushed (i.e. deoptimization).

Comments
EVALUATION See main CR
12-09-2011

EVALUATION http://hg.openjdk.java.net/hsx/hotspot-rt/hotspot/rev/fdb992d83a87
23-08-2011

EVALUATION http://hg.openjdk.java.net/hsx/hotspot-comp/hotspot/rev/fdb992d83a87
16-08-2011

EVALUATION This optimization should only be applied to MutableCallSite objects and not VolatileCallSite objects since the latter are intended to change their targets very often which would lead to very bad performance.
27-07-2011