Ted Hong
Ted Hong
Currently DSLX does not support specification of recursive functions -- https://github.com/google/xls/issues/510 Many logic functions such as reduce_or, clz, etc... can be implemented via a tree of reduction logic. One way...
For a few operations (ex. div by certain constants), LLVM JIT will instead rely on functions implemented within its runtime library (built-ins) like __udivti3. This issue is to either 1)...
So that designers can utilize assertions akin to the assertions they are used to in SV, DSLX/XLS should support somthing akin to SV's LTL assertions. Note that one complication is...
Related google/xls#869 and google/xls#656 While top-level channel naming as improved due to google/xls#656 -- internal channels created within the config block of a proc are named with arbitrary line numbers...
Sometimes, it is desirable to not auto format sections of code (ex. comments that should not be reflow'ed). This issue is to support such a mechanism.
### What's hard to do? (limit 100 words) Often requested is a peek() op that given a streaming channel, will return the data at the head of the channel (if...
### What's hard to do? (limit 100 words) Currently IR supports the addition of a MIN_DELAY op to impose scheduling constraint between two nodes. This should be exposed to DSLX....
### What's hard to do? (limit 100 words) Currently we can specify constraints between send/recv nodes. Our schedule also support pinning a particular node to a stage -- https://github.com/google/xls/blob/f231771f048112e74e23f9134a56606c16cdf634/xls/scheduling/scheduling_options.h#L119 But...
### What's hard to do? (limit 100 words) Currently I/O options for channels are global and specified as side-band options. https://google.github.io/xls/codegen_options This is too generic and often we would like...
### 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...