[sv-cc] SV-CC Meeting minutes for 11/10/2004

From: Charles Dawson <chas@cadence.com>
Date: Wed Nov 10 2004 - 12:51:30 PST

Minutes of 11/10/2004 SV-CC Meeting.

ATTENDEES
0000000000
4444444444
1111110000
1100009999
1022102211
0360369250
xxxxxxxxxx Charles Dawson
xxxxxxxxxx Francoise Martinolle
xxxxxxxxxx Doug Warmke
xxxxxx-xxx Bassam Tabbara
xxxxxxxxxx Andrzej Litwiniuk
xxxxxxxxxx Joao Geada
xxxxxx-xxx Jim Vellenga
xxxxxxxxx- Ralph Duncan
xxxxx--x-- Rob Slater
xxxxxx-x-- Sachchidananda Patel
xxxxxxxx-- Michael Rohleder
xxxx-xxx-- John Stickley
xxxxxxx-x- Jim Garnett
xxxxxx--x- Steven Dovich
xxx-x-xxxx Ghassan Khoory
---------x Swapnajit Mitra
---------x Karen Pieper
-------x-- Angshuman Saha
---x------ Kevin Cameron
-x-------- Amit Kohli
x--------- Surrendra Dudani

1. Reviewed Patent information.

   - Charles Dawson read the patent information.

2. Reviewed minutes of the 10/26/04 Meeting.

   - Francoise and Ralph think Ghassan abstained on 205.
   - JimV/Doug. Minutes accepted as amended.

3. Liaisons

   - Francoise talked briefly about EC and BC committees.

1800 meeting last week of Nov. 22.
   - No other meetings were reported on.

4. New business

   - Conducted a brief discussion on SystemVerilog and System-C.
     Steve pointed out that the discussion is out of scope.
     Rob thought that the SV-CC is already talking about interfacing
     two things: SystemVerilog and C. Steve thinks we DASC should create
     a new working group for this kind of activity.
   - Discussed new items: 277, 278, 280, 281, 282, 283, 284, 288. 289, 292, 293, 294, 295
     Chas asked for volunteers for these un-assigned items.
     JimV willing to take all the ones that he added. Steve will take 278.
     JimV wanted clarification on 282. Chas didn't like option 3 - already
     decided? Steve thinks it should be implementation specific.
     JimV asked about 295. There were no objections to getting rid of
     "var bit typespec". Michael will take 288. Chas will assign rest to those
     who do not have a heavy burden already.
   - Discussed remaining schedule.
     Francoise pointed out that 1800 meeting will be 11/22/2004.
     Chas said that issues passed today would be considered for that meeting. Chas
     wanted to make sure we would have quorum for the 11/24/2004 meeting. Yes.
     We have 3 meetings left to finish things. Everyone to look at remaining items
     and point out any that must be resolved before ballot!
   - Surrendra had a question about embedded NULL characters and
     what would the issue be for DPI? The LRM doesn't clearly state
     it but in some places it looks like you could have embedded NULL
     characters in the string. String then becomes an array of char.
     Won't be able to pass it as a string, need to pass it as array and
     pass the size as well. Wanted to know if it is a problem, and
     whether the proposal should be to change LRM to not allow it.

5. Reviewed of items with proposals.

   - Item 277: Spelling error in Table 31-4 "Instance" not "Instances"

     Discussed. Joao/JimV PASSED (unanimous)

   - Item 060: bad cross-reference in notes 3 and 4 of diagram 31.10

     Discussed. Ralph/JimV PASSED (unanimous)

   - Item 201: More details needed on DPI string argument handling

     Decided to defer because of strings in systemVerilog may have
     imbedded NULLs. Doug and Michael will research further.

   - Item 274: Small 2-state type svBitVec32 provokes C coding difficulties

     John expressed that this is an issue for him in his models.
     Joao would like to add an example. Doug will add the example
     at the bottom of his bugnote.
     Doug/John PASSED (unanimous)

   - Item 280 List of new vpiOpType operators is incomplete and redundant

     Straw poll: Francoise/JimV Accepted. (abstain: Michael)

   - Item 281 31.10 Variables supersedes two sections

     Francoise pointed out that this won't be "1364-2001". Need to find
     all references and fix. Francoise to file errata issue. Chas to
     bring up at next 1800 committee.
     Straw poll: Joao/JimG Accepted (unanimous)

   - Item 283 Wrong outline and font for VPI array var objects

     Straw poll: JimV/Joao Accepted (unanimous)

   - Item 265 sv_vpi_user.h has redundancy

     JimV found a some issues. Bassam will work on it some more.

6. Old Business

   - Chas asked that everyone go through the action items and let him
     know if any could be removed from the list.

Meeting ended at 1:05pm (EDT)

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.
   - Joao/Francoise to file SV-BC item asking to define linearization.
   - Francoise to check with SV-BC on default return type of functions.
   - Chas to ask Karen about updating the diagrams (does not fit well
     with approved process).
   - Andrzej to make sure the LRM says that for the C layer of DPI,
     representations of a type are always the same regardless of where
     it is (packed struct, member of array, ...etc.).
   - Francoise and Bassam to reconcile sections 28 and 31.
   - Doug to add last example in bug note to proposal in Item 274.
   - Francoise to add Item that will call for replacement of "1364-2001"
     references with an up to date reference.
   - Chas to point out to IEEE 1800 committee that the references to
     "1364-2001" are out of date.
   - Everyone to review outstanding items to make sure high priority ones
     are resolved prior to 12/1/2004

   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.
   - All to review Generates proposal from ETF committee.
   - Francoise, et all to review BTF generates proposal
     for the upcoming vote, with particular emphasis on
     how we will address generates in VPI.
   - 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.
   - Stu to write an addition to the proposal for PTF 342.
     This will cover that PLI 1.0 was deprecated in section 20
     and include some of the stuff currently in section 21
     (like the descriptions for the checktf and calltf).
   - 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 optional.
   - Chas to re-verify the cross references are properly updated for PTF 342.
   - Chas to add to proposal for PTF 342 a reference to the prior version of the
     specification

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

   - Item 265 sv_vpi_user.h has redundancy
   - Item 061 Meaning of vpiMultiArray depends on 1364 but is in conflict with it
   - Item 065 Note 19 in section 31.10 is wrong
   - Item 058 type of vpiTagged property in 31.12 is wrong
   - Item 072 LRM specifies number references for vpi defines, only to be done in annex
   - Item 288 Use a proper typedef for 32-bit values instead of 'unsigned int'

--
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 Nov 10 12:51:38 2004

This archive was generated by hypermail 2.1.8 : Wed Nov 10 2004 - 12:51:47 PST