verilator fails to regenerate cpp code when verilog source is updated #707
Labels
area: configure/compiling
Issue involves configuring or compilating Verilator itself
resolution: fixed
Closed; fixed
Author Name: Derek Lockhart
Original Redmine Issue: 707 from https://www.veripool.org
Original Date: 2014-01-17
Running Verilator 3.855 devel rev verilator_3_854-8-gb5f5b1f on OSX Mavericks, verilator fails to regenerate cpp code when verilog source is updated. This problem is intermittent, but reproducible.
Given some simple verilog source:
Changing the name of the output signal and running verilator does not consistently regenerate cpp source.
Below shows a bash session in which I perform the following steps:
I've tried many variations in an attempt to find a pattern. Sometimes code generation works just fine, and each time the source is change cpp code is regenerated. Other times I can change the source, and run verilator many times without success.
I could not find any flags that enable a 'force recompile' option with the verilator docs, so I'm not sure if this is due to a timestamp/caching issue within verilator. Running with --debug did seem to fix the issue, but I would prefer not to have the extra output generated by the debug build.
The text was updated successfully, but these errors were encountered: