#434 Use of task to assign reg value: internal error

v0.8
closed-fixed
nobody
5
2008-05-13
2008-05-09
TonyCas
No

Using a task to assign a global reg value causes the following error:

:0: internal error: NetProc::nex_output not implemented
:0: : on object type 8NetUTask

A test case file is attached.

Discussion

  • TonyCas

    TonyCas - 2008-05-09
     
  • Cary R.

    Cary R. - 2008-05-12

    Logged In: YES
    user_id=1651735
    Originator: NO

    FYI this works correctly with the latest development version.

     
  • TonyCas

    TonyCas - 2008-05-13

    Logged In: YES
    user_id=2074732
    Originator: YES

    It turns out that this bug is related to the presence of the (*) sensitivity list. If the sensitivity list is explicitly filled out then the file compiles OK.

     
  • Cary R.

    Cary R. - 2008-05-13

    Logged In: YES
    user_id=1651735
    Originator: NO

    The ultimate explanation is that this bug is related to a user function called within a block using * in the sensitivity list. A patch that mirrors what the development branch does for this case is available in the patch tracker. The compiler no longer crashes, so I am assuming the code will now work correctly.

     
  • Cary R.

    Cary R. - 2008-05-13
    • status: open --> closed
     
  • Cary R.

    Cary R. - 2008-05-13
    • status: closed --> closed-fixed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks