verilator DUT cpp generation bug

[stevobailey]

Running a Verilator test twice doesn't reproduce the DUT cpp code. This can be seen by first generating a DUT with a Vec IO of some size, and then generating a DUT with the Vec IO size increased.

I don't have a solution, but I wrote a test that fails.

[shunshou]

Same problem I've already posted about, I think. There's a bunch of stale code. My only way around is to create a new directory every time you generate something and before you do sbt test or w/e, delete your existing directories.

I've gotten thrown off by this issue several times -- wondering why tests passed/failed when they should've failed/passed, but no one's bothered to do anything about this yet.