2015-11-23 21:21 GMT+01:00 Tristan Gingold <tging...@free.fr>: > On 21/11/15 01:37, Peter LaDow wrote: > >> On Fri, Nov 20, 2015 at 2:52 PM, <why...@f-cpu.org> 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? 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. Ralf
_______________________________________________ Ghdl-discuss mailing list Ghdl-discuss@gna.org https://mail.gna.org/listinfo/ghdl-discuss
