|
Quick Lists
|
|
Bug ID:
|
6260293
|
|
Votes
|
0
|
|
Synopsis
|
fix set_ctrl() inconsistencies in loopopts
|
|
Category
|
hotspot:compiler2
|
|
Reported Against
|
|
|
Release Fixed
|
mustang(b49),
5.0u19(b01) (Bug ID:2158032)
, 5.0u18-rev(b03) (Bug ID:2174003)
|
|
State
|
10-Fix Delivered,
request for enhancement
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
6435614
,
6548082
,
6644519
,
6659207
,
6233005
|
|
Submit Date
|
22-APR-2005
|
|
Description
|
In loopopts, we sometimes use set_ctrl() and friends to associate a node with a control that we wouldn't allow as in(0). For example, we may call set_ctrl() with an IfNode.
Such sloppiness can cause surprising results downstream where we compare in(0) against get_ctrl() and do a particular transformation based on that comparison.
Such loose play lead to problems such as found in 6233005.
xxxxx@xxxxx 2005-04-22 21:40:23 GMT
|
|
Work Around
|
N/A
|
|
Evaluation
|
Add assert in loopnode.hpp wherever we call _nodes.map. Let the asserts be our
guide in finding bad ctrl settings.
xxxxx@xxxxx 2005-04-22 21:46:19 GMT
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
