Re: [PATCH v3 09/13] verification/rvgen: Delete __parse_constraint()

Gabriele Monaco [off-list ref] writes:

Yeah, I don't see it explicitly mandated in the theory, but the
description (from the sources) states:

  The value of a clock thus denotes the amount of time that has been  
elapsed since its last reset

But it also says (emphasis added by me):

  Clocks /can/ be reset to zero after which they start increasing ...

Nowhere it says clocks /must/ be reset, their value simply won't make
sense (according to the definition).

Now in our implementation we may have some automatic reset when the
monitor starts (I'm planning that to avoid invalid states), which could
make explicit resets superfluous in some cases.

Reseting the clocks on monitor start sounds sensible.

Let's leave that to the user for now and skip this check.

Thanks,
Nam