Open hongted opened 2 months ago
Currently procs can block for multiple reasons. For XLS's interpreters' purposes, a Tick() can return once procs are blocked and progress is made.
https://github.com/google/xls/blob/1578b44caac9cc63fc96924f09197d1d03dcd64c/xls/interpreter/proc_runtime.h#L119-L129
This issue is to enhance
#1000
Related: https://github.com/google/xls/issues/1538 https://github.com/google/xls/issues/1527
None
DSLX should have a barrier or a WaitAndHoldProcsAtStart() built-in.
~Sorry if I'm missing something, but what does issue #1000 have to do with this?~ (Fixed in original)
That's just GFM messing things up. It's suppose to be Verilog delay control IIUC.
What's hard to do? (limit 100 words)
Currently procs can block for multiple reasons. For XLS's interpreters' purposes, a Tick() can return once procs are blocked and progress is made.
https://github.com/google/xls/blob/1578b44caac9cc63fc96924f09197d1d03dcd64c/xls/interpreter/proc_runtime.h#L119-L129
This issue is to enhance
#1000
Related: https://github.com/google/xls/issues/1538 https://github.com/google/xls/issues/1527
Current best alternative workaround (limit 100 words)
None
Your view of the "best case XLS enhancement" (limit 100 words)
DSLX should have a barrier or a WaitAndHoldProcsAtStart() built-in.