Subject: RE: Assertions API v0.3
From: Bassam Tabbara (bassam@novas.com)
Date: Tue Jan 14 2003 - 16:48:09 PST
Well the API is directed at all the consumers (I think...), isn't it ?
Granted implementing the API in VPI form may cloud the picture a bit,
but that's a decision we made on implementation not restricting
functionality. Doing on the fly is not that strange (common case is
configuration as you state)... BTW, having this freedom to send a
directive (without changing source) even a TOOL-specific directive is
pretty useful....
Thx.
-Bassam.
> 1.1: is such control of assertions directive something that
> can be done on the fly
> *in the middle of simulation* ? That is the effect of
> extending such
> control via VPI. I believe what you want is reasonable,
> but this is
> something that would apply to temporal properties to all
> consumers
> (simulation, coverage, formal tools, hw accelerators,
> etc), and as
> such would appear something best expressed as a design
> configuration or similar.
This archive was generated by hypermail 2b28 : Tue Jan 14 2003 - 16:49:18 PST