475 karma · joined June 23, 2015
Former backend engineer / labor union data monkey.
paul at silogy io
I've used it myself. It has some rough edges in terms of rendering performance but it's nice overall.
I strongly recommend that anyone doing civil disobedience join up with an organization which can provide training, logistical support, and at least some degree of legal support. The first two are if anything even more important given that these situations tend to be chaotic and tense. The book Waging a Good War documents the intensive training that activists underwent during the civil rights movement which was crucial for their success.
Of course the situation is much more lawless now in places like Minneapolis and ICE is much more undisciplined than the police, which makes civil disobedience much more challenging and dangerous. That just makes training and legal aid all the more necessary.
To steelman what you're saying, it's true we lived with it so long that it came to seem normal in a way if you weren't personally affected. But "everyone has been silent" is just not true.
Bhutan vs the West is a huge difference in comparison.
We at Silogy [0] are directly targeting the problem of verification productivity using AI agents for test debugging. We analyze code (RTL, testbench, specs, etc.) along with logs and waveforms, and incorporate interactive feedback from the engineer as needed to refine the hypothesis.
I've also heard from various people that although Verilator is generally fast, it tends to choke on compiling sufficiently large designs, whereas the Cadence and Synopsys offerings eventually get it done.
Still, Verilator is an awesome piece of software. Maybe the biggest thing recommending it: it's totally free, so the number of simulations you run in parallel is bounded by compute availability rather than licenses.
Shameless plug: I'm a cofounder of silogy.io, which offers hosted Verilator and other Verilog sims, plus debugging and collab tools.
I think a lot of her books are about how many different ways of life and types of society and culture are possible, and this book is one of her best at bringing you in to another culture.
Bash is just an example; most people should make the test rule call the simulator executable directly or via a thin wrapper script. MyHDL is interesting too. Admittedly this is the first we've heard of it but we'll take a look.
We are working on supporting additional simulators in addition to Verilator.
Also, we are working on an API and command line tool so you can kick off test runs and view the results from the command line. This CLI tool should also support local test runs at some point.
For the other problems you mentioned: we're currently just handling the verification piece of the puzzle for right now, we want to do one thing really well first. We feel your pain on the SystemVerilog code generation front, we've had to interact with similarly primitive code generation mechanisms. You can only go so far with the preprocessor and what gets generated during elaboration.
Cost for cloud vs on prem is very specific to design complexity. For the designs we're working with, we have seen that compute is cost effective on the cloud with respect to building out on-prem compute. We expect that to change as we support larger designs, and we have support for on-prem compute firmly on our roadmap.