Thanks for the observations. It's true that every company that needs this eventually figures something out.
The difference is (a) our customers don't want to be in the devops business, and for startups especially it's a severe barrier to entry that we can make disappear, and (b) we are going to keep investing in our products (especially collaboration tools and integrations with waveforms, logs, etc) long past the point where a chip company would decide their internal tools are "good enough" (hint: they're generally not).
UVM support is one of the next items on our priority list.
Comments
Thanks for the observations. It's true that every company that needs this eventually figures something out.
The difference is (a) our customers don't want to be in the devops business, and for startups especially it's a severe barrier to entry that we can make disappear, and (b) we are going to keep investing in our products (especially collaboration tools and integrations with waveforms, logs, etc) long past the point where a chip company would decide their internal tools are "good enough" (hint: they're generally not).
UVM support is one of the next items on our priority list.
I noticed there are some GitHub Repos actively working on enabling UVM on Verilator:
https://github.com/MikeCovrado/GettingVerilatorStartedWithUV...
It would be an amazing leap to enable UVM fully on Verilator. Looking forward to it.