[sv-cc] SV-CC agenda for 12/01/2004

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 11:30am EST (4:30pm GMT), and last for 1.5 hours.

Some of the old business below involve items which we have already passed, or
intend to address at this meeting. It's going to be a long meeting, but I
think it is important that we spend a few minutes making sure we have addressed
these particular action items. Therefore, I would ask that you take a look
ahead of time, and at the end of the meeting I would like to quickly go through
them. Thanks.

     -Chas

AGENDA

1. Review Patent information

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

2. Review minutes from last meeting (11/24/2004)

3. Liaisons

   - Anyone care to make a report?

4. New business

   - Items 41, 51, 169
   - Item 45 - Should it be "Immediate"?
   - Review all remaining items which do not have a proposal and are marked
     as "Immediate". By my count, there are at most 19 such Items.
   - Others?

5. Review SV-CC items with proposals:

   - Item 265 sv_vpi_user.h has redundancy
   - Item 313 PTF 296: Generate stmts will need change made in VPI
   - Item 307 PTF 530: 26.6.17: expr class does not contain vpiTchkTerm - should model different
   - Item 318 Utility fn to reveal if packed type actual form == canonical form
   - Item 309 PTF 622: Return value for left/right range of unsize parameter
   - Item 278 contradiction between example 3 in E.9.4 and specification for packed arrays embedded in aggregates
   - Item 301 Is every unpacked array a VPI array var?
   - Item 160 multiple packed array dimensions (E.6.6, E.10.1 differences)
   - Item 292 vpi_handle_by_multi_index return types
   - Item 293 Clean up vpiWaiting/Process typo
   - Item 289 In VPI model, "mod port" should be one word
   - Item 061 Meaning of vpiMultiArray depends on 1364 but is in conflict with it
   - Item 318 Utility fn to reveal if packed type actual form == canonical form
   - Item 049 Necessity of specifying import fn return type
   - Item 267 VPI model for randcase statements (section 12.15)
   - Item 311 PTF 329: 27.29: vpi_put_data not used in example
   - Item 310 PTF 623: 26.6.15 should not be modeled with multiple labels on one transition
   - Item 040 diagram for parameter is missing
   - Item 312 PTF 368: 26.3.3 Should vpiLineNo and vpiFile apply to generate objs?
   - Item 308 PTF 605: describe better which condifion trigger action callbacks

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.
   - 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.
   - Everyone to review outstanding items to make sure high priority ones
     are resolved prior to 12/1/2004
   - Doug to update Item 201.
   - Michael to update Item 288.
   - Chas to update Item 303.
   - Francoise and Chas to review Item 265's proposal.
   - Stu to see if older versions of IEEE standards are still available.

   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.
   - 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.

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