[sv-cc] RE: [sv-ac] SV-AC and SV-BC collaboration mode

Done.

 

Dmitry

 

________________________________

From: Lisa Piper [mailto:piper@cadence.com] 
Sent: Thursday, March 06, 2008 12:28 AM
To: Korchemny, Dmitry; Charlie Dawson
Cc: sv-cc@eda-stds.org; sv-ac@eda.org
Subject: RE: [sv-ac] SV-AC and SV-BC collaboration mode

 

Please add 1503 to this list.  I believe SV-CC has had some discussions
on this already but it is not complete.

 

Lisa

 

________________________________

From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of
Korchemny, Dmitry
Sent: Tuesday, March 04, 2008 8:11 PM
To: Charlie Dawson
Cc: sv-cc@eda-stds.org; sv-ac@eda.org
Subject: [sv-ac] SV-AC and SV-BC collaboration mode

 

Hi Charles,

 

I would like to elaborate the coordination mode between SV-AC and SV-CC
for working on the VPI related SV-AC proposals. I suggest that the
proposal owners work closely with SV-CC on their proposals and attend
SV-AC meetings when their proposals are discussed.

 

In case the SV-CC bandwidth does not allow operative handling of all the
SV-AC proposals, would it be possible to identify the SV-CC volunteers
to review the proposals before they are officially reviewed by SV-CC?

 

Could you, please, provide the time line of handling the SV-AC proposals
and the schedule of their discussion, in order to allow the proposal
owners to attend relevant discussions, and to work on their proposals
with SV-CC?

 

Here is the list of the VPI-related SV-AC proposals:

 

. 1599 API and VPI changes for 0805 (Bassam Tabarra)

. 1757 accept_on/reject_on (Doron Bustan)

. 1898 Explicit mappings from assertion system tasks to callbacks
(Bassam Tabarra)

. 2005 Glitches with immediate assertions (Erik Seligman)

. 2182 VPI diagrams for checkers (Erik Seligman)

. 2250 VPI changes for LTL operators(Erik Seligman)

 

Thanks,

Dmitry

---------------------------------------------------------------------
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 <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.