| ▲ | IshKebab 2 hours ago | |||||||
It's just a shame that (System)Verilog is such an awful awful language. And we're basically stuck with it, at least for ASICs, despite the availability of alternative HDLs that compile to SV. | ||||||||
| ▲ | taldo 2 hours ago | parent | next [-] | |||||||
I worked for a couple of years in a SystemVerilog compiler, and I couldn't agree more with your sentiment. From the compiler construction standpoint, it's grossly underspecified, to the point that our customers' designs were way more expressive than the spec. And from the users' perspective, it's confusing, quite limited, and you end up having to resort to hacks to achieve what should be part of the language... Fortunately I can't remember any particularly bad examples, it's been 15 or so years since I left for greener pastures. Still, I sometimes wonder, how much of HW design is influenced by the language decisions, these ugly hacks, and the emerging (System)Verilog design patterns? Could it be measurably better in a different world? | ||||||||
| ||||||||
| ▲ | tialaramex 41 minutes ago | parent | prev | next [-] | |||||||
Could we fix that do you think? I think 25 years ago I would not have believed we would ever fix (La)TeX but here's Typst. | ||||||||
| ▲ | kreyenborgi 2 hours ago | parent | prev | next [-] | |||||||
Will I have the same learning effect if I use https://github.com/clash-lang/clash-compiler instead of straight verilog, or is the language a necessary part of it? | ||||||||
| ||||||||
| ▲ | Lramseyer 2 hours ago | parent | prev [-] | |||||||
It's awful by design! Do you know how much Cadence, Synopsys, and Siemens profit off of the bloated LRM? | ||||||||