Subject: FW: [sv-cc] assertion API
From: Joao Geada (Joao.Geada@synopsys.com)
Date: Wed Apr 16 2003 - 14:31:43 PDT
Oops, forgot to forward this to sv-cc
==============================================================================
Joao Geada, PhD Principal Engineer Verif Tech Group
Synopsys, Inc TEL: (508) 263-8083
377 Simarano Drive, Suite 300, FAX: (508) 263-8069
Marlboro, MA 01752, USA
==============================================================================
-----Original Message-----
From: Joao Geada [mailto:joao@synopsys.com]
Sent: Wednesday, April 16, 2003 5:11 PM
To: Francoise Martinolle
Subject: RE: [sv-cc] assertion API
Hi Francoise,
All those should be removed from the API. At the time we wrote it, these were
being considered by SV-AC, but they seemed not to have made it.
Joao
==============================================================================
Joao Geada, PhD Principal Engineer Verif Tech Group
Synopsys, Inc TEL: (508) 263-8083
377 Simarano Drive, Suite 300, FAX: (508) 263-8069
Marlboro, MA 01752, USA
==============================================================================
-----Original Message-----
From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org]On Behalf Of
Francoise Martinolle
Sent: Wednesday, April 16, 2003 5:01 PM
To: sv-cc@eda.org
Subject: [sv-cc] assertion API
After reviewing the assertion chapter, I thought it would be good to review
again
the assertion API chapter.
While doing do, I found no correlation between some of the directive
properties:
vpiAssumeAssertion, vpiRestrictAssertion etc, with the assertion chapter.
Should this really be in our API or should we remove some of these properties
directive because they are not in the language anymore.
Francoise
'
This archive was generated by hypermail 2b28 : Wed Apr 16 2003 - 14:33:07 PDT