Catherine
Catherine
I agree this is valuable. Please submit a patch. I'll review the overall architecture.
I would accept a PR implementing that.
(Agreed on both counts.)
According to Clifford, the `TRANSPARENT` parameter of `$memrd` only applies to the ports in the same domain, so point (2) does not necessarily apply. (It would be still be necessary...
According to UG473, `WRITE_FIRST` (i.e. transparent) ports are *recommended* for TDP, and `READ_FIRST` ports would, confusingly, result in an undefined value being read. This doesn't seem to make any sense...
According to @nakengelhardt, a read/write collision between asynchronous ports *always* results in undefined data being read. Apparently, using the `WRITE_FIRST` is recommended because it results in lower power consumption. Based...
Reopening per discussion in https://github.com/YosysHQ/yosys/issues/1390.
After careful consideration, it is my opinion that `transparent_for` should be used as soon as possible, even if it means desugaring to `\TRANSPARENT=1` in Yosys at first. Including in 0.1.
After discussion with Yosys maintainers, the most likely way this will be solved upstream is by (a) keeping `\TRANSPARENT` working as it currently is, (b) splitting ports into groups (which...
Looking at how things go, I will get around to docs somewhere around November-December. A number of other people are blocked on SoC-adjacent improvements (simulator, CSR, streams) so I want...