JDK-6582890 : assert(cost >= 0,"negative spill cost")
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2007-07-19
  • Updated: 2013-01-29
  • Resolved: 2011-03-08
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
6u10Fixed 7Fixed hs11Fixed
Related Reports
Relates :  
JDK-6510732 - Compute consistent block frequencies
Description
Running specjbb2005 in x86 -d32 may produce this assertion.
The following nightly tests (at least) are affected:-

gc/memory/Churn/Churn1
Comments
SUGGESTED FIX PRT webrev: http://prt-web.sfbay.sun.com/net/prt-archiver.sfbay/data/archived_workspaces/main/c2_baseline/2007/20070725144056.rasbold.c2_baseline0/workspace/webrevs/webrev-2007.07.25/index.html
26-07-2007
EVALUATION The computation of consistent frequencies relies on the reasonable probabilities for IfNodes. A predicted call is generating a probability greater than 1, which causes the block frequency estimator to propagate a negative frequency. As a result, ifg.cpp crashes with an assertion. The inaccuracies of method data profiling may raise the probability of a predicated call to appear to be slightly greater than 1. The compiler needs to clamp such values to something more sane, like PROB_MAX.
19-07-2007