JDK-5074577 : Bad performance when HotSpot cannot optimize polymorphic calls
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 6
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_9
  • CPU: sparc
  • Submitted: 2004-07-15
  • Updated: 2005-09-28
  • Resolved: 2005-09-28
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 JDK 6
5.0u8Fixed 6 b54Fixed
Related Reports
Relates :  
Only the second suggested fix for the bug 4803284 was integrated into Tiger:

  "Don't generate stack overflow check when a compiled method doesn't have 
   java calls and has frame size < vm_page_size/8."

The first suggested fix required more time for investigation.

SUGGESTED FIX Webrev: http://analemma.sfbay.sun.com/net/prt-archiver.sfbay/data/archived_workspaces/main/c2_baseline/2005/20050920142945.kvn.5074577/workspace/webrevs/webrev-2005.09.20/index.html Add C2 product flag BimorphicInlining and set the default value to true. Save information about all known receivers from method_data in ciCallProfile. Sort the information by calls count. Inline (or direct call) second method if the call site is bimorphic and the flag BimorphicInlining is true. Set probability on dynamic class check based on the virtual call profile info. It shows double performance improvement on the original test cases from 4803284 but it doesn't improve our benchmarks scores. *** (#1 of 1): [ UNSAVED ] ###@###.###

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang

EVALUATION ###@###.### 2004-07-15 I have fix for this but need more time for testing. Committed to Mustang.