Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#1 Forced value doesn't propagate through expressions

devel
closed-fixed
nobody
6
2005-11-26
2005-10-04
Stephen Williams
No

[Transferred from ivl-bugs PR#699]

In the appended test (bug.v) the forced value of b
does not propagate through to the d result.

Discussion

  • Test for the symptom

     
    Attachments
  • Logged In: YES
    user_id=97566

    Bug persists in 0.8 release. Set group to devel.

     
    • milestone: 530239 --> devel
     
  • Logged In: YES
    user_id=97566

    The bug.v sample attached to this report has been added to
    the ivtest suite as pr699.v.

     
  • Logged In: YES
    user_id=97566

    pr529.v (attached) is a more elaborate test of a whole host
    of force situations. This seems to cover the whole host of
    issues. This test program was originally submitted by
    sjs@pobox.com

     
  • More elaborate test from ivl-bugs pr#529

     
    Attachments
  • Another sample from ivl-bugs PR#587

     
    Attachments
  • Logged In: YES
    user_id=97566

    The pr587.v file is from ivl-bugs PR#587, which is yet
    another report that seems to stem from the same issue. The
    submitter in that case was Aaron Holtzman
    <aholtzma@ess4.engr.uvic.ca>. His original text was:

    When I force a wire, the value doesn't propogate down to any
    modules that are connected to that wire. Here is an example
    to illustrate the problem

     
    • priority: 5 --> 6
     
    • status: open --> open-fixed
     
  • Logged In: YES
    user_id=97566

    Tests pr587.v, pr529.v and pr699.v in the ivtest suite pass
    as of the CVS main trunk of 26 Nov 2005. The last fix checked
    in was for force l-values that are bit/part selects.

     
    • status: open-fixed --> closed-fixed