| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2158032 | 5.0u19 | Dmitriy Samersoff | P2 | Resolved | Fixed | b01 |
| JDK-2174003 | 5.0u18-rev | Dmitriy Samersoff | P4 | Resolved | Fixed | b03 |
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.
###@###.### 2005-04-22 21:40:23 GMT
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.
###@###.### 2005-04-22 21:40:23 GMT
- backported by
-
JDK-2158032 fix set_ctrl() inconsistencies in loopopts
-
- Resolved
-
-
-
- Resolved
-
- duplicates
-
JDK-6644519 5u12 64bit fails with SIGBUS in interpreted code
-
- Closed
-
- relates to
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
(2 relates to)