Subject: Proposed requirements for SV assertion API
From: Joao Geada (Joao.Geada@synopsys.com)
Date: Wed Aug 14 2002 - 14:14:20 PDT
Assertion API Requirements:
1- Provide means (eg iterator) to obtain every assertion within a given instance
2- Provide means to obtain every assertion associated with a given module
(sum of all assertions in all instances of the given module)
3- Provide means to get handle to an assertion by name
4- Provide means to control assertions:
4.1 enable an assertion
4.2 disable an assertion
4.3 reset an assertion
6- Provide means for applications to register callbacks for:
6.1 assertion success
6.2 assertion failure
6.3 assertion attempt
6.4 assertion being disabled
6.5 assertion being enabled
6.6 assertion being reset
7- Provide means to obtain per assertion static information:
7.1 assertion type (eg check/forbid/event/...)
7.2 assertion attributes (eg assume/guarantee/...)
7.3 source information (source file, line number, ...)
7.4 clocking signal/expression
7.5 instance in which assertion exists
7.6 name of assertion
7.7 module in which assertion declared
9- Provide means to obtain information about a specific success/failure:
9.1 time assertion attempt started
9.2 signal/expression where success/failure detected
==============================================================================
Joao Geada, PhD Sr. Staff R&D Engineer Verif Tech Group
Synopsys, Inc TEL: (508) 263-8083
154 Crane Meadow Road, Suite 300, FAX: (508) 263-8069
Marlboro, MA 01752, USA
==============================================================================
This archive was generated by hypermail 2b28 : Wed Aug 14 2002 - 14:16:24 PDT