Jump to content

Recommended Posts

Posted

The delay argument to nb_transport_fw/bw is declared as an input, whereas the delay argument to b_transport is not an input, and is thus in effect a non-const reference. In SystemC TLM-2.0 the delay arguments to each of these calls are non-const, and are intended to be used in the same way for temporal decoupling with both blocking- and non-blocking transport.

The UVM implementation is in effect creating a difference in the timing annotation mechanism between the blocking- and non-blocking cases, which is not justified by the TLM-2.0 standard. So I guess that

- either this was not intentional, and should be fixed

- or was intentional, and should be documented accordingly

- or nobody cares and we should leave well alone ;)

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...