Jump to content

Dynamic processes and initialization phase


Recommended Posts


I created a dynamic process during the evaluation phase and added dont_initialize() to the process. Now, the process will not be added to the runnable processes queue.

But Initialization phase is already over. How this dont_initialize() affects the execution of this dynamic process. What SystemC kernel is doing with dont_initialize() for this process.


Is dont_initialize() just a way to hold addition of the process to the runnable process queue in the same evaluation phase?

Thanks !

Link to comment
Share on other sites

Yes, creating a process with dont_initialize() set just keeps it off the runnable queue until it is triggered by its static sensitivity (or through an explicit reset() on a process handle of it).  Without dont_initialize(), static process are marked as runnable during the initialization phase, while dynamic processes are made runnable immediately (i.e. in the current/next evaluation phase).

Hope that helps,

Link to comment
Share on other sites

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.

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...