How are non-deterministic inputs handled

[Timmmm]

How does TestRig handle non-deterministic values, or at least values that will naturally differ from implementation to implementation, e.g:

• Time (mtime)
• Interrupts
• CSRs (mvendorid etc)

If you inject some instructions that do any of those it will give different results for different CPU implementations, and I can't see any mechanism to avoid that.

[PeterRugg]

Oops, not sure why I didn't see this until now! For the record, this is a gap in TestRIG's functionality: either you ensure your implementations line up, or you avoid testing that feature. We have discussed some other ways to work around it, but there are no immediate plans to implement anything.

[marnovandermaas]

I'm reopening this issue and labelling it as enhancement for a future release.