![[logo]](/img/veripool_small.png)
Issue #18
make $dumpfile(), $dumpvars() no-op when --trace is disabled
| Status: | WillNotFix | Start date: | 07/05/2008 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
or, alternatively, use occurences of $dumpfile(), $dumpvars() to let verilator decide whether to generate the trace code or not? Right now the user has to touch two switches (the command line and the source) to enable tracing.
History
Updated by Wilson Snyder almost 5 years ago
- Status changed from New to WillNotFix
Er, $dumpfile etc isn't ever supported and I think making them error only when tracing is on will just confuse people; enabling waves to debug something shouldn't generate new errors.
Unfortunately, using $dumpfile etc to control tracing won't work with SystemC, nor when there is more than one Verilated model in the design, so I don't want to deal with it otherwise.
Also available in: Atom