Remix.run Logo
▲ nomel 3 hours ago

> Verilog

My favorite side quest that I definitely recommend. Physical parallelism is so fun to reason about.

I had the advantage of sitting next to a proper professional to bounces questions off of, so I was able to get an SPDIF decoder to work in about a week! It was a very interesting lesson in the costs of abstraction, and why you will never really find abstraction layers in hardware.

▲pastel8739 4 minutes ago | parent | next [-]

> why you will never really find abstraction layers in hardware

This is interesting to me, in the very little HDL I’ve done there were abstractions: you set up modules with inputs and outputs that provided a consistent interface despite complexity inside the model. Is this not what you mean by abstraction layer?

▲IshKebab 2 hours ago | parent | prev | next [-]

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?

▲rcxdude 2 hours ago | parent [-]

Yeah, using (system)verilog is essentially a process of "think of the digital circuit you want, then figure out how to write it as a 'sequential' process so that the compiler can then generate the circuit you want". The way it works feels quite clever when you first learn about it but the way it works in practice is bizarre.

▲tialaramex 36 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?

▲rowanG077 an hour ago | parent [-]

As the maintainer of clash I would say yes definitely! Clash is at the same level of hardware specifications as VHDL and verilog. You lay down every wire and register. It's just that you get all the niceties of Haskell, the very powerful type system and abstraction capabilities.

▲Lramseyer an hour ago | parent | prev [-]

It's awful by design! Do you know how much Cadence, Synopsys, and Siemens profit off of the bloated LRM?

▲Grimblewald 2 hours ago | parent | prev [-]

This sounds quite interesting to me, if you have the time, could you please elaborate a bit on the cost of abstraction?