[sv-cc] SV-CC Meeting minutes for 12/08/2004

From: Charles Dawson <chas@cadence.com>
Date: Wed Dec 08 2004 - 15:02:25 PST

Minutes of 12/08/2004 SV-CC Meeting.

ATTENDEES
00000000000000
44444444444444
11111111110000
22111100009999
00211022102211
81470360369250
xxxxxxxxxxxxxx Charles Dawson
x-xxxxxxxxxxxx Francoise Martinolle
xxxxxxxxxxxxxx Doug Warmke
xxxxxxxxxx-xxx Bassam Tabbara
xx-xxxxxxxxxxx Andrzej Litwiniuk
x--xxxxxxxxxxx Joao Geada
xxxxxxxxxx-xxx Jim Vellenga
xxxxxxxxxxxxx- Ralph Duncan
-x-xxxxxx--x-- Rob Slater
-xxxxxxxxx-x-- Sachchidananda Patel
xxxxxxxxxxxx-- Michael Rohleder
x--xxxxx-xxx-- John Stickley
xxxxxxxxxxx-x- Jim Garnett
xxxxxxxxxx--x- Steven Dovich
-x-xxxx-x-xxxx Ghassan Khoory
-------------x Swapnajit Mitra
-------------x Karen Pieper
-----------x-- Angshuman Saha
-------x------ Kevin Cameron
-----x-------- Amit Kohli
----x--------- Surrendra Dudani
xxx----------- Stu Sutherland

1. Reviewed Patent information.

   - Charles Dawson read the patent information.

2. Reviewed minutes of the 12/01/04 Meeting.

   - Doug/Joao. Accepted.

3. Liaisons

   - Chas/Francoise to report on Champions meeting.

     Zero replication. We need to take a look at that one.
     BTF item 547. Uwire and types on nets.
     Joao and Doug were there too.
   - SV-EC meeting. They decided that strings should not
     have NULL characters.
   - No other meetings were reported on.

4. New business

   - 201 More details needed on DPI string argument handling

     Motion to reconsider approval of 201: Steve/Joao. ACCEPTED
     Motion to amend proposal for 201: Doug/JimV. ACCEPTED
     Motion to accept proposal: Doug/JimV. PASSED

   - 050 Change DPI svLogicVec32 representation to match PLI/VPI aval/bval representation

     Motion to reconsider: Doug/Joao. ACCEPTED

     Most agreed in principle to the proposal made by Oz. Doug would like to go a step
     further and eliminate some of the DPI routines. Andrzej was concerned about
     the standard restricting implementors in the way that the data is stored.

     Motion to table: Steve/JimV. ACCEPTED

     Joao took an action to setup a separate meeting to discuss.

   - 064 Note 20 of section 31.10 is unclear

     Motion to re-consider: Francoise/Dovich ACCEPTED
     Motion to table: Francoise/JimG. ACCEPTED
     Francoise and JimG will write a new proposal.
     There was discussion about the lack of clarity in the specification on the
     return values for many of the properties. It would be good to have a table
     for each property like vpiScalar and vpiVector and their return values.
     JimV to enter a new SV-CC item for future consideration.

   - 333 VPI support for types on wires

     Michael is concerned about how extensive of this proposal was at this late
     date. Francoise was unclear on access to cont assigns from nets.
     Francoise to discuss further with JimV. It was clear that more time was
     needed to review the proposal. ALL to review for next week.

   - 053 VPI access to instances and packages is incorrect

     Chas reported that he has a proposal almost ready to go. Should be out
     shortly.

   Meeting ended at 1:05pm (EST)

   - 054 What is the vpiFullName of a package?

     Chas reported that there is a bugnote that has been added indicating his
     idea on how to proceed, and he asked the committee to review and comment
     on the idea.

   - 055 fullnames of declarations in the global scope of a compilation unit

     Chas reported that there is a bugnote that has been added indicating his
     idea on how to proceed, and he asked the committee to review and comment
     on the idea.

   - 056 vpi_handle_by_name on imported items?

     Chas reported that there is a bugnote that has been added indicating his
     idea on how to proceed, and he asked the committee to review and comment
     on the idea.

   - 062 Conflicting vpiArray property descriptions in 31.10
   - 077 VPI diagram for instances shouldn't refer to reg objects
   - 332 VPI support for new uwire net type

     JimV reported that there is a simple solution already in the description,
     so this one should be easy.

5. Reviewed of items with proposals.

   - None.

6. Old Business

Meeting ended at 1:05pm (EST)

7. Action items

   SV-CC action items:
   - Francoise to ask Peter Ashenden what was done to improve
     printing from Rational Rose.
   - Francoise to inquire about the feasibility of third parties
     shipping the UML for the diagrams.
   - Sachi to drive finding a better solution for 052.
   - Chas to add Stu to SV-CC email alias.
   - JimV to enter a new SV-CC item for adding tables for return values of
     the properties.
   - Joao to setup a meeting to discuss Item 050.
   - ALL to review proposal for Item 333 for next meeting.

   PTF action items:
   - Steve to compare BNF with the access available
     for attributes to see if they match
   - Francoise to remove "+" from tags in UML diagrams and
     add vpi prefix where appropriate.
   - Francoise to send out HTML for 1364-2001 diagrams, using
     something other than JPG for importing diagrams into frame.
   - Stu to write proposal for PTF 368.
   - Francoise to write proposals for PTF 373, 374, and 396.
   - Steve to write proposals for PTF 311, and 495.
   - Sachi to write proposals for PTF 307, 312, and 313.
   - Stu to enter new PTF item for save/restart/reset issue.
   - JimG to write proposals for PTF 517, 533, and 534.
   - Chas to write proposal for PTF 296.
   - Francoise to lookup wording for PTF 524 in VHPI.
   - Francoise will open a new PTF issue to look for situations like 25.6.15,
     where multiple methods are used access the same object enclosure
   - Chas to reword proposal for PTF 525.
   - Draft a straw man proposal using a clean slate with no concern for
     existing PLI/VPI on the best way to represent all Verilog and
     SystemVerilog kinds and types. This straw man will then be used as a
     basis for discussing backward compatibility with the existing reg, net,
     variables, functions, and parameter diagrams. It may be decided that
     full backward compatibility is not possible, or is not the best approach
     moving forward.
   - Sachi will file a PTF item for the clarification of what can be done
     at ROsync time and putting values in future times.
   - Francoise to file a PTF item that asks to specify the order that iteration
     occur in, when the order is important.
   - Steve to add ETF item for Annex C to remove the Informative label, but
     still allow the contents to be option

8. Items for consideration at the next meeting (they already have proposals):

   - 333 VPI support for types on wires

--
Charles Dawson
Senior Engineering Manager
NC-Verilog Team
Cadence Design Systems, Inc.
270 Billerica Road
Chelmsford, MA  01824
(978) 262 - 6273
chas@cadence.com
Received on Wed Dec 8 15:02:33 2004

This archive was generated by hypermail 2.1.8 : Wed Dec 08 2004 - 15:02:36 PST