Odp.: RE: [sv-cc] vpiAssertLockCovered

From: <radoslaw.nawrot@aldec.com.pl>
Date: Mon Oct 06 2014 - 23:33:30 PDT
Thanks
Pozdrawiam,
Radosław Nawrot

-----Original Message-----
From: "Bresticker, Shalom" <shalom.bresticker@intel.com>
Date: Mon, 6 Oct 2014 14:22:03 
To: Radosław Nawrot<Radoslaw.Nawrot@aldec.com.pl>; sv-cc@eda.org<sv-cc@eda.org>
Subject: RE: [sv-cc] vpiAssertLockCovered

I filed this request as Mantis 5037.

From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On Behalf Of Rados?aw Nawrot
Sent: Tuesday, September 30, 2014 12:35
To: sv-cc@eda.org
Subject: [sv-cc] vpiAssertLockCovered

Hello,
IEEE1800-2012 provide possibility to loack and unlock assertion from VPI assertion API.
There is lack of that information in assertion-specific coverage status properties.
Maybe we need define  vpiAssertLockCovered property ?

In

40.5.3 Obtaining coverage information:



vpi_get(vpiAssertLockCovered, assertion_handle)

returns the number of times the assertion has been locked.


Best regards,
Radek


--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Mon Oct 6 23:34:08 2014

This archive was generated by hypermail 2.1.8 : Mon Oct 06 2014 - 23:34:16 PDT