This would be be (by orders of magnitude?) the most complex design attempted in the language, which pushes it into NIH territory.
This would be be (by orders of magnitude?) the most complex design attempted in the language, which pushes it into NIH territory.
also, you may be interested to know: Sorbonne University has access to Cadence. after converting to Verilog, they ran our 180nm design through DRC and it passed 100%.
nmigen has some deterministic behavioural guarantees and much more which make it a far better choice. it happens to output Verilog which we can treat as a (readable) machine-code (assembler-like) intermediary.
It's for sure a solvable problem, but 9 time out of 10 the FOSS developers trying to push a new language into this space end up not meeting their actual "release a usable design" goals but instead spend all their time yak shaving the language. It's a classic nerd snipe in the space.
right now we're in like "R&D mode", thankfully paid-for by NLnet.
i go into some detail about why we chose nmigen, and what can be done with it. it was not a "light decision", it was several months comprehensive review.
here's the point in the FOSDEM talk i just did: https://youtu.be/7rCeNzrCB_g?t=1939