Subject: RE: [sv-cc] Date: Thu, 17 Apr 2003 11:27:56 -0400
From: Joao Geada (Joao.Geada@synopsys.com)
Date: Thu Apr 17 2003 - 08:46:51 PDT
Francoise,
this is described in section 27.5.2, towards the end of the section, when
vpi_control(vpiAssertionEnableStep, assertionHandle, attempt, vpiAssertionClockSteps)
is described. I do not see any issue in regard to this.
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: Thursday, April 17, 2003 11:28 AM
To: joao.geada@synopsys.COM
Cc: sv-cc@eda.org
Subject: [sv-cc] Date: Thu, 17 Apr 2003 11:27:56 -0400
Question:
IN section 27.4.2 Two callback reasons are provided and the comment is made that the step callbacks are only enabled on a per assertion per attempt basis.
How do you register that specific callback and specify which thread if you
can only pass a handle to the assertion instance?
reference:
cbAssertionStepSucess
the progress of one “thread” along an attempt. By default, step callbacks are not enabled on any assertions;
they are enabled on a per-assertion/per-attempt basis, rather than on a per-assertion basis.
cbAssertionStepFailure
failure to progress along one “thread” along an attempt. By default, step callbacks are not enabled on any
assertions; they are enabled on a per-assertion/per-attempt basis, rather than on a per-assertion basis.
Francoise
'
This archive was generated by hypermail 2b28 : Thu Apr 17 2003 - 08:48:18 PDT