[sv-ac] FW: [sv-cc] Next IEEE 1800 WG Meeting -- SV-CC presentation?

fyi

From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On Behalf Of Rados?aw Nawrot
Sent: Friday, February 13, 2015 18:41
To: 'Jim Vellenga'; sv-cc@eda.org
Cc: 'Karen Pieper'
Subject: RE: [sv-cc] Next IEEE 1800 WG Meeting -- SV-CC presentation?

Hi Jim, hi all
Most important issues (for me):
-- 0004619: VPI inconsistency between array ports and array nets http://www.eda-twiki.org/svdb/view.php?id=4619
-- 0004238: VPI for elements and members of aggregate parameters http://www.eda-twiki.org/svdb/view.php?id=4238
-- 0004104: Clarify use of svSize() and other DPI access functions when open array matches multidim array with variable sizes http://www.eda-twiki.org/svdb/view.php?id=4104 . We should be able do detect such cases
-- Checkers in VPI
-- Way to dectect virtual interface connection (0004733: Callbacks on virtual interface var - proposal - or similar)

nice to  have :
-- 0004620: Need VPI support for interconnect nets and ports http://www.eda-twiki.org/svdb/view.php?id=4620
-- 0005037: vpiAssertLockCovered http://www.eda-twiki.org/svdb/view.php?id=5037
-- Streaming expressions in VPI
Regards,
Radek Nawrot
________________________________
From: owner-sv-cc@eda.org<mailto:owner-sv-cc@eda.org> [mailto:owner-sv-cc@eda.org] On Behalf Of Jim Vellenga
Sent: Friday, February 13, 2015 5:23 PM
To: sv-cc@eda.org<mailto:sv-cc@eda.org>
Cc: Karen Pieper
Subject: RE: [sv-cc] Next IEEE 1800 WG Meeting -- SV-CC presentation?
Since Charles resigned as chair, the SV-CC currently has no leader.  So I am sending this out to SV-CC to see what our other participants see as key issues.

If you reply to all (or reply to me), I'll gather up a list for someone (any volunteers?) to present at the March 6 meeting of the Working Group.

Cadence has worked on or at least has looked at dealing with the following SV-CC issues:

-- Clarification of vpiOrigin and vpiParent relations for frames

-- VPI support for user-defined nettypes ("6.6.7 User-defined nettypes")

-- VPI support for generic interconnect ("6.6.8 Generic interconnect")

-- VPI support for streaming operator expressions ("11.4.14 Streaming operators (pack/unpack)")

-- VPI support for elements and members of typed parameters

-- VPI support for checkers

-- Clarification of VPI relations for threads

-- Clarification (?) of vpiSize property values for mixed and/or multi-dimensional dynamic (QDA) arrays

-- Corrections/clarification of support for instance & instance arrays (instance arrays include primitive arrays, but instances do not include primitives)

In addition, a customer has requested the ability to transmit a 4-state unpacked struct across the DPI interface.

Regards,
Jim Vellenga

From: owner-sv-cc@eda.org<mailto:owner-sv-cc@eda.org> [mailto:owner-sv-cc@eda.org] On Behalf Of Karen Pieper
Sent: Wednesday, February 11, 2015 7:21 PM
To: IEEE 1800; SV-AC eda.org; SV-BC eda.org; SV-CC eda.org; Sv-ec; SV-DC; SV Champions
Subject: [sv-cc] Next IEEE 1800 WG Meeting

Hi, all,

As we discussed in our last meeting, the next IEEE 1800 WG will be Friday March 6 from 9am to 1pm at Cadence.

The agenda can be found here:

http://www.eda-twiki.org/cgi-bin/view.cgi/P1800/P1800Agendas

More details will be available soon,

Karen



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

--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.
--
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.