On 05/04/15 18:03, Adam Jensen wrote:
On Sun, 05 Apr 2015 11:08:44 +0200
Tristan Gingold <[email protected]> wrote:
On 03/04/15 17:42, Adam Jensen wrote:
Does the --time-resolution flag exist in the tip version?
This option is supported only when time is on 32 bit, which is not
anymore the case.
Would it be a lot of work or challenging in some other way to restore the
time-resolution capability? With the time-resolution fixed to femto seconds,
the total simulation time is limited to about 2.6 hours.
2^63 * 1e-15 sec ~= 153.723 min
If events in a model occur on the scale of minutes, the simulations are very
limited.
Note that the current (disabled) implementation might not be
very intuitive. For example, if you select time resolution as us,
you have:
1 ms = 1000 us,
1 s = 1000_000 us,
...
and 1 ps = 0 us, 1 fs = 0 us, 1 ns = 0 us.
That looks obvious. But the consequences aren't:
10 ns = 0 us
100 ns = 0 us
1000 ns = 0 us
...
ie it is as if: 1000 ns = 1000 * 1 ns = 0 us
Tristan.
_______________________________________________
Ghdl-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/ghdl-discuss
