Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6260293

fix set_ctrl() inconsistencies in loopopts

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 5.0u12, 6
    • Fix Version/s: 6
    • Component/s: hotspot
    • Labels:
      None
    • Subcomponent:
    • Resolved In Build:
      b49
    • CPU:
      generic, sparc
    • OS:
      generic, solaris

      Backports

        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.
        ###@###.### 2005-04-22 21:40:23 GMT

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  rasbold Chuck Rasbold
                  Reporter:
                  rasbold Chuck Rasbold
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Imported:
                    Indexed: