Approved Minutes of Apr-22-2009 SV-CC Meeting.

ATTENDEES

00
99
00
44
20
28
xx Charles Dawson
xx Jim Vellenga
xx Chuck Berking
xx Francoise Martinolle
xx Abigail Moorhouse
xx John Shields
xx Michael Rohleder
xx Amit Kohli
x- Ying-Tsai Chang

1. Reviewed Patent information

- Chas reviewed the patent information which can be found at http://standards.ieee.org/board/pat/pat-slideset.ppt

2. Approval of agenda

Jim/Chuck APPROVED

3. Review minutes from last meeting (Apr-08-2009)

    Chuck/Jim.  ACCEPTED

4. Liaisons

  - Chas commented on the P1800 meeting.
    Amit will ask for DPI section source (chas to ask Stu).

  - Francoise discussed the SV-EC meeting
    Two ballot comments on scheduling: they agree we should keep for future use. 
    Need to respond that we will not be addressing them at this time.
    Chas and Francoise will work on putting together response.
    Other committees will be doing email votes.
  - No other meetings to report on.

5. Consent Agenda

6. Expedited Agenda Items

7. New business

  • Suspend normal operating procedure - allow proposals with less than 2 weeks notice?

  Chuck/Abi  ACCEPTED

  • Discuss schedule - Can we complete ballot items before May-14-2009?

  There are no other issues which are of concern.

  • Next meeting

  Abi thinks we should meet next week.   Jim thinks we should take it one week at a time.
  Chas will schedule a meeting for next week.
  Chuck would like 2622 as Not a Bug for concent agenda.

8. Reviewed items with proposals

9. Reviewed SV-CC items with proposals (Straw poll only)

  • 1775 cbAtEndOfSimTime not in header files

  Jim/Chuck PASSED (unanimous)

  • 2572 sv_vpi_user.h (Annex N source) needs repairs

  Chuck has two proposals, the second includes a vpiInsideOp.  Abi has no opinion.  Francoise
  thinks we should add it.  Michael agrees.  Suspended discussion until end so Abi can investigate
  further and so that we can add more things if necessary.  Francoise thinks we should try to
  compile with the include files.  Abi and Chuck have both done that.

  • 2576 Failed to remove reference to Reader API when deprecating Data Read API

  Francoise/Abi.  PASSED (unanimous)

  • 2621 Ballot comment #155 vpiSize should return an error when applied on a vpiFunction returning string

  Third iteration on this proposal.  Jim thanked everyone for their feedback.  Made the proposal better.
  Jim noted that vpiReturn does not come from function, but that was not reported as a ballot comment.
  Friendly amendment to change  (see 37.14, detail 9) to  (see 37.17, detail 9).
  Chuck moves to accept as modified.  Jim seconds.  PASSED (unanimous)
  Jim updated the proposal.

  • 2623 Ballot comment #157 vpiArrayType is labelled bool, should be int

  Chuck/Jim.  PASSED (unanimous)

  • 2626 Ballot comment #162 In Table 38-3 in vpiScalarVal, vpi1 et al should be in bold

  Jim/Michael.  PASSED (unanimous)

  • 2631 Ballot comment #172 The usage of the the term PLI is confusing

   Friendly amendment to change "two different interface" to "the two different interfaces" in section.
   Chuck/Abi move to pass as amended.  PASSED (unanimous)
   Chas updated the proposal.

  • 2637 Ballot comment #146 Term PLI is confusing

  Jim/Michael.  PASSED (unanimous)

  • 2628 Ballot comment #164 In Arguments section, s_vpi_arrayvalue should be p_vpi_arrayvalue.

  Francoise noted that it is not in the header files.  Chuck commented that that is in the proposal for 1775.
  Chuck/Francoise.   PASSED (unanimous) 

Motion to adjourn: Francoise/Chuck. Meeting ended at 1:02 pm.

10. Old Business

11. Action items

%ACTIONSEARCH{ state="(?!closed).*" topic="SVCCActionList" }%

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

13. Next meeting

The next SV-CC meeting will be on Apr-29-2009.

The next P1800 meeting will be on May-14-2009.

-- ChasDawson - 22 Apr 2009

Topic revision: r3 - 2009-04-29 - 16:28:24 - ChasDawson
 
Copyright © 2008-2026 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback