|
Quick Lists
|
|
Bug ID:
|
5015073
|
|
Votes
|
1
|
|
Synopsis
|
CastPP removal process is too complex
|
|
Category
|
hotspot:compiler2
|
|
Reported Against
|
1.5
|
|
Release Fixed
|
|
|
State
|
3-Accepted,
request for enhancement
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
4959717
|
|
Submit Date
|
17-MAR-2004
|
|
Description
|
CastPP nodes are generally removed after the CCP pass.
This is done by a convoluted process using the Ideal_DU_postCCP virtual functions in which CastPP nodes are made useless by tricking their types. Any MemNode outputs of these CastPP nodes that would then require a control edge are updated by walking up their input address nodes looking for an appropriate CastPP or CheckCastPP node. The MemNode inherits its control from the found cast node.
With DU edges available, it seems simpler to eliminate CastPP nodes and walking their output edges, updating the control inputs of the output nodes.
|
|
Work Around
|
N/A
|
|
Evaluation
|
With DU edges available, it seems simpler to eliminate CastPP nodes and walking their output edges, updating the control inputs of the output nodes.
If we retain MemNode:Ideal_DU_PostCCP in some form, the control flow within in the while(true) loop needs to be cleaned up.
xxxxx@xxxxx 2004-03-17
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |