[sv-cc] SV-CC agenda for 04/11/2005

Hi All,

The call-in information for this meeting is as follows:

   U.S.               866-807-0627
   International      203-955-5179
   Passcode           399143

Meeting will start at 10:00am EDT (2:00pm GMT), and last for 5.0 hours.

   -Chas


AGENDA

1.  Review Patent information

   Go to:
     http://standards.ieee.org/board/pat/pat-slideset.ppt

2.  Review minutes from last meeting (04/08/2005)
   - JimV noted two minor issues.

3.  Liaisons

   - Anyone care to make a report?

4.  New business

   - Review trivial ballot comments mantis items
     - Item 542 26.2.4 inconsistency
     - Item 540 26.1 inconsistency
     - Item 415 26.6.3 improperly drawn diagram - regression
     - Item 414 26.6.42 'taskfunc' should be 'task func'
     - Item 413 Need parens at end of routine call properties
   - Item 465
   - Item 464
   - Item 612
   - Item 613
   - Item 605
   - Others?

5.  Review SV-CC items with proposals:

   - Item 600 32.22 Confusing statement about vpiActualDefn
   - Item 474 32.22 remove notes 5 and 6
   - Item 533 32.22 vpiAccessType should be vpiVisibility
   - Item 610 32.22 vpiFullName for data members?
   - Item 475 32.23 property return values should be specified in include file
   - Item 478 32.26 property type is missing
   - Item 602 32.26 "vpiVisibility" rather than "vpiAccess" for task and function declaration
   - Item 482 32.27 Don't need vpiBuiltIn property
   - Item 494 32.40 diffs here vs the include file
   - Item 497 32.45 typespec reference should be a expr reference - regression
   - Item 440 Annex I - vpiUserDefinedClass
   - Item 531 Annex I - no declaration of vpiUnboundConst
   - Item 495 32.40, 32.41, and 32.42 all supersede P1364 26.6.27
   - Item 425 29.3.2.1 violates a principle design feature of VPI
   - Item 422 29.1.1 should be removed
   - Item 423 29.2 This section is no longer needed
   - Item 427 29.3.2.2 should be removed
   - Item 431 29.5 pollutes the VPI name space
   - Item 432 29.5.2 Don't understand note at the end
   - Item 426 29.3.2.1 Return value of vpi_get_assertion_info() is backwards
   - Item 433 30 - incorrect title
   - Item 434 30.1.3 Last sentence is not clear
   - Item 586 31.8.7 sentence need clarification
   - Item 585 31.8.6 font issue
   - Item 455 32.12.1 poorly written paragraphs
   - Item 489 32.38 Need better definition of a ref obj object.
   - Item 447 32.5 missing types for properties
   - Item 526 VPI references to dynamic objects prevent garbage collection
   - Item 372 PTF 312: Need two new time related callbacks
   - Item 417 PTF 311 Problem with loads in VPI
   - Item 605 32.2 & 32.3 & 32.6 vpiDefaultClocking is not in include file
   - Item 463 32.16 should not perpetuate unused functionality
   - Item 600 32.22 Confusing statement about vpiActualDefn

6.  Review SV-CC items with proposals (Straw poll only):

7.  Review old business:

   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.
   - JimV to enter a new SV-CC item for adding tables for return values of
     the properties.
   - Stu to file new SV-CC item that will address bigger issue he pointed
     out in Item 321.
   - Francoise and Chas to investigate what to do for systemVerilog and generates
   - Chas to redo proposal for Item 372.
   - Chas to redo proposal for Item 417.
   - Bassam to redo proposal for Item 605.
   - Chas/Francoise to review/change proposal for Item 455.
   - Chas to redo proposal for Item 463.
   - Chas to ask the P1800 committee for some period of time after the other
     committees have completed their work so that the SV-CC can react to their
     changes.

   PTF action items:
   - Steve to compare BNF with the access available
     for attributes to see if they match
   - Stu to enter new PTF item for save/restart/reset issue.
   - 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.
   - 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 file an Item on the usage of the term "tags" at the beginning of
     clause 27.

-- 
Charles Dawson
Senior Engineering Manager
NC-Verilog Team
Cadence Design Systems, Inc.
270 Billerica Road
Chelmsford, MA  01824
(978) 262 - 6273
chas@cadence.com