JDK-7097679 : Tiered: events with bad bci to Gotos reduced from Ifs
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: hs20
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-10-04
  • Updated: 2012-01-23
  • Resolved: 2012-01-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 8 Other
8Fixed hs23Fixed
Description
In case with back branches Runtime1::counter_overflow() routine expects to receive a bci of either a Goto of If instruction that generated
the event. When emitting the counter overflow stub for the goto we take the bci from the jvm state. However it is not correct for the gotos 
that were produced as a result of the reduction of Ifs because this case the state will have a bci that would possibly point to a Cmp

Comments
EVALUATION See main CR
28-10-2011

EVALUATION http://hg.openjdk.java.net/hsx/hotspot-comp/hotspot/rev/940513efe83a
04-10-2011

SUGGESTED FIX The solution is to always store a proper bci for Goto and use it instead of the one in the jvm state.
04-10-2011