Subject: Suggestions needed for coverage API
From: Joao Geada (Joao.Geada@synopsys.com)
Date: Thu Jan 16 2003 - 08:04:32 PST
Hi all,
I am putting together the coverage API proposal. My current thought is to
follow the same path as the assertion API and make the proposal in terms of
extensions to the VPI interface. The coverage API thus is likely to consist
of the following parts:
1- a SV "language side" set of "built-in" system tasks related to realtime
coverage (probably not much different than the original donation)
2- a set of VPI extensions aimed at designers/verification engineers to
obtain coverage
3- more detailed set of VPI extensions aimed at tool providers
(these listed in priority order)
For items 2 & 3, representing line, toggle and assertion coverage is relatively
straightforward (grab a handle to the item in question and ask "is it covered?")
However, there is neither a representation for FSMs in VPI and nor any "natural"
handle to which such information could be attached.
My request is: how would you propose that FSM coverage be represented?
(with the usual constraints on simplicity, elegance & sufficiency)
Thanks for all suggestions in advance,
Joao
==============================================================================
Joao Geada, PhD Principal Engineer Verif Tech Group
Synopsys, Inc TEL: (508) 263-8083
344 Simarano Drive, Suite 300, FAX: (508) 263-8069
Marlboro, MA 01752, USA
==============================================================================
This archive was generated by hypermail 2b28 : Thu Jan 16 2003 - 08:06:10 PST