<alyssa>
Despite Amaranth not integrating with Verilator officially, Amaranth->Verilog->Verilator seemed less... experimental? then cxxrtl
<alyssa>
(And Pysim would be too slow, both because of the simulation perf itself and also the overhead of generating reference vectors in Python vs C)
<alyssa>
and also I wanted an excuse to learn how to use Verilator without having to write Verilog :-p
<vup>
Hmm cxxsim is quite experimental. But cxxrtl not (or atleast not as much). Tbh I never used verilator, so I dont actually know how they compare, but it always looked a bit hmm more complicated I guess.
<alyssa>
Oh, maybe I mixed those up
<alyssa>
At any rate, I got my frankestein amaranth+verilator setup working and exhaustively tested a module in $fast, so that's nice
<alyssa>
now just need to add gtest and openmp into the frankenmix :-p
<adamgreig[m]>
I ended up using pytest to handle building and executing the c++ files from verilator and/or cxxrtl to avoid gtest 🙈
<alyssa>
adamgreig[m]: It might be the stockholm syndrome from $DAYJOB but what's wrong with gtest? :)
<adamgreig[m]>
hah, just the opposite I guess, I've used pytest so much and haven't touched gtest in a decade
<adamgreig[m]>
all my tests using pysim are in pytest so it was nice to have the c++ ones be part of the same test suite