On 25/11/15 15:12, Ralf Hallmen wrote:
2015-11-23 21:21 GMT+01:00 Tristan Gingold <[email protected] <mailto:[email protected]>>:On 21/11/15 01:37, Peter LaDow wrote: On Fri, Nov 20, 2015 at 2:52 PM, <[email protected] <mailto:[email protected]>> wrote: I suppose: because they can change several times during a delta cycle, so the final value would be irrelevant. If you want to spy on them, make your own "log" (with "report"s) or copy them to a dedicated signal. GHDL can work under GDB so you can also trace/single step the generated program. For my part, I'd like to see delta cycles logged. We have some testbench code that operates in delta cycles (zero time), and that's impossible to see in GHDL. You can use --disp-signals. There is no tool that is able to display delta cycles :-( You probably mean no tool for GHDL?
More generally, no open-source tool and no open-source wave format.
Because Modelsim can display delta cycles and I already had some use cases where that was really helpful. It works in the waveform and you will see the current time + current number of delta cycles.
I agree it could be really useful. Tristan. _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
