[sv-cc] SV-CC agenda for 04/08/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/05/2005)

3.  Liaisons

   - Anyone care to make a report?

4.  New business

   - Review trivial ballot comments mantis items
     - Item 603 "callee's declared the formals"?
     - Item 591 31.11 vpi_get_time() is a void routine - backwards compatibility
     - Item 582 31.8.4.2 grammar
     - Item 574 31.8.3.2 Typo
     - Item 569 31.8.1 typos
     - Item 535 32.26 font size of note is inconsistent
     - Item 530 Annex E - Examples should use DPI-C label
     - Item 527 32.14 grammatical error
     - Item 525 32.13 grammatical error
     - Item 504 32.53 Missing info from P1364 26.6.42
     - Item 503 32.52 'return stmt' should be 'return'
     - Item 498 32.50 minor clarification needed here
     - Item 491 32.40 Missing null stmt definition
     - Item 479 32.26 'refobj' should be 'ref obj'.
     - Item 476 32.23 clarify vpiParent label
     - Item 471 32.21 typo in note 6
     - Item 466 32.20 'nets' should be 'scope'
     - Item 462 32.14 vpiParent label is poorly placed
     - Item 461 32.30 indentation for properties is incorrect
     - Item 446 32.5 incorrect note
     - Item 444 32.3 & 32.6 Superfluous note should be removed
     - Item 443 32.2 The note needs to go in section 32.7
     - Item 428 29.4.2 needs better whitespace
     - Item 502 32.51 vpiExpr should apply to entire disables class
     - Item 500 32.47 Implies all expressions have a vpiName property
     - Item 490 32.39 Indexed part select is missing
     - Item 488 32.38 vpiMemory should be removed
     - Item 477 32.25 missing newer changes from P1364
     - Item 457 32.13 LHS of bottom diagram incorrectly drawn
     - Item 456 32.13 poorly drawn diagram - regression

   - Items that can be closed:
     - Item 379 27. VPI Routine Definitions - section describing optional arguments
     - Item 337 Informative table on VPI sections not up-to-date
     - Item 297 Need to replace all occurences of IEEE 1364-2001 with new standard version name
     - Item 338 31.22 missing from Table of Contents

   - Other items that have proposals:
     - Item 386 Erroneous cross-reference in E.6.6
     - Item 385 Incorrect DPI return type allowed in 28.4.5
     - Item 406 scalar bit and logic small values omitted from E.7.7 definition
     - Item 407 clarify support for enumeration base types (E.6.3)


   - Others?

5.  Review SV-CC items with proposals:
   - Item 470 32.21 Properties should be with defn not ref
   - Item 460 32.13  need parens at end of routine properties
   - Item 447 32.5 missing types for properties
   - Item 439 Annex I - implied properties are really return values
   - Item 566 31.6 Why is there a double line between vpi_iterate() and vpi_handle()?
   - Item 536 Annex E.6.2 - packed struct and union types with DPI
   - Item 372 PTF 312: Need two new time related callbacks
   - Item 417 PTF 311 Problem with loads in VPI
   - Item 524 32.13 & 32.14 vpiArrayMember and vpiMember
   - Item 382 vpiMember rather than vpiMembers in object model for nets
   - Item 453 Several sections missing access by index properties
   - Item 605 32.2 & 32.3 & 32.6 vpiDefaultClocking is not in include file
   - Item 448 32.8 First note is not necessary and is incorrect
   - Item 452 32.8 backwards compatibility broken here
   - Item 455 32.12.1 poorly written paragraphs
   - Item 463 32.16 should not perpetuate unused functionality
   - Item 469 32.21 Note 2 is a partial sentence
   - Item 468 32.21 First note needs some work
   - Item 467 32.21 extend or extends?
   - Item 599 32.22 Clarify vpiActualDefn
   - 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 polutes 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


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

   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