Paul Rigge
Paul Rigge
I'm just jotting down some thoughts on priority select optimizations we could do but aren't doing yet, feel free to add more. * If `p_i` is the `i`th selector bit...
It looks like some examples are using reserved identifiers[^1]. Related #477 [^1]: https://groups.google.com/g/xls-dev/c/bRyh3VCuXfc
Right now, prove_quickcheck_main dumps the counterexample property. Ideally, for fast interactive testing, it should dump a test suitable for interpreter_main, i.e. ``` #![quickcheck] fn prop_A(x) -> bool { f(x) }...
An upcoming change will move channel legalization strictness from being a global option to a per-channel option. For example, one channel could be configured as requiring mutually exclusive usages while...
Mutually exclusive side effects with a token relationship can cause (avoidable?) scheduling problems
If two side-effecting operations that are ordered by a token relationship have mutually exclusive predicates, the token relationship can be removed. Removing this token can be useful in scheduling. For...
Currently, the `FifoConfig` construct has fields for fifo `depth` and `bypass`. Bypass, which is not carefully specified, may imply combinational coupling between push- and pop-side signals. The combinational coupling between...
In a current WiP change, I'm putting FIFO state in the register state map. This is convenient and avoids the need for API changes, but has some shortcomings. Long term,...
### What's hard to do? (limit 100 words) Ideally, XLS codegen would have more customization around how it instantiates FIFOs, perhaps via a format string or whatever more sophisticated method...
### What's hard to do? (limit 100 words) Currently, we don't block-convert new-style procs (e.g. those with proc-scoped channels and proc instances). This means that procs that are instantiated multiple...
### What's hard to do? (limit 100 words) Channel legalization is starting to feel like proc inlining more and more, both because it's big and because it does a lot...