|
From: Stephen W. <st...@ic...> - 2016-04-08 14:41:22
|
For the scheduling part, there is an internal attribute that elaboration can attach to the process (the NetProc instance?) to adjust scheduling at startup. That would probably be the best way to handle it. On 4/8/16 1:09 AM, Martin Whitaker wrote: > Alan Manuel Gloria wrote: >> In particular, always_comb is not precisely the same as always@*; >> always_comb executes its contents at startup immediately, then blocks on >> sensitivity list. So instead of always@* begin foo; bar; end, it's more >> like always begin foo; bar; @*; end This hack is because constant wires >> and parameters might not trigger @*, leading to an RTL-vs-gate mismatch >> during simulation startup if you use always@*. > > That's not too hard to implement. What will take more work will be the differences in the implied > sensitivity list - in particular the sensitivity to the contents of called functions. Then there's > the additional checks for delays and multiple assignments... > > Martin > > ------------------------------------------------------------------------------ > _______________________________________________ > Iverilog-devel mailing list > Ive...@li... > https://lists.sourceforge.net/lists/listinfo/iverilog-devel > -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." |