JDK-6212007 : low frequency basic blocks are not moved out of line
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 6
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2004-12-23
  • Updated: 2010-04-02
  • Resolved: 2005-09-22
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
6 b53Fixed
Related Reports
Relates :  
JDK-5003419 - empty blocks sometimes produce unnecessary jumps
Description
Basic blocks that implement the slow path of a memory allocation stay inline with
the fast path.  It is the intent of the server compiler to have them (and other uncommonly executed blocks) be placed elsewhere, mostly likely near the end of the function.
###@###.### 2004-12-23 00:23:45 GMT
Comments
SUGGESTED FIX See PRT webrev: http://analemma.sfbay.sun.com/net/prt-archiver.sfbay/data/archived_workspaces/main/c2_baseline/2005/20050914133524.rasbold.c2_baseline/workspace/webrevs/webrev-2005.09.15/index.html
15-09-2005
EVALUATION The removeEmpty() pass in the code generator has a fairly dumb algorithm. ###@###.### 2005-03-04 20:59:28 GMT
23-12-2004