[sv-cc] Meeting minutes for 04/25/2007

From: Charlie Dawson <chas_at_.....>
Date: Mon Apr 30 2007 - 07:55:00 PDT
Minutes of 04/25/2007 SV-CC Meeting.

ATTENDEES
000000000000000000
777777777666666666
000000000111110000
443322111221009988
212121310200212131
518484173068517306
xxxxxx-xxxxxxxxxxx Charles Dawson
xxx-xxxxxxx-x-xxxx Ralph Duncan
xxxxxxxxxxxxxxxxxx Jim Vellenga
xxxxxxxx-xxx-x-xxx Andrzej Litwiniuk
xxxx-xxxxx-xxxxxxx Abigail Moorhouse
xxx-xxxx--xxxxxx-x Michael Rohleder
xxxx-xxxxxxxxxxxxx Chuck Berking
xxxxxxxxxxxx-xxxxx Bassam Tabbara
xx-xx-xx-x-xxxxxxx Francoise Martinolle
xxxxxx-xxxxxxxxxx- Ghassan Khoory
-----xx----------- Steve Dovich
--x--xxxx----xx-xx Amit Kohli
--x--------------- Stu Sutherland
x----------------- Gord Vreugdenhil

1.  Reviewed Patent information.

   - Chas reviewed the patent information.


2.  Reviewed minutes of the 04/11/2007 Meeting.
     - Ralph/Chuck.  ACCEPTED


3.  Liaisons
   - Chas commented on the P1800 meeting. 890  Going ahead with merged doc.
   - Francoise has no other meetings to report.
   - No other meetings to report on.


4.  New business

   - Gord's tf_nodeinfo() question
     Michael thinks we should force people to go to VPI.  There is no
     reason for it.  Too many other issues are coming up.  Abi agrees.
     Chas commented that the main concern is for accessing memories
     efficiently.  Michael suggested accessing memories as a packed array
     of words.  Jim pointed out that there were cases where customers
     did not want to propagate the values.  Abi asked when we would be
     encroaching on DPI.  Michael thought that the use model for the
     two interfaces are different.  Gord commented that if we went too
     far in VPI, the implementations would be fully constrained.
     Gord thinks that it might be a reasonable option to consciously
     decide that vendors would provide a proprietary solution for the
     performance issues.  Francoise suggested a function tray idea for
     dealing with the memory performance.  Michael liked the idea.
     Michael proposed that we should do some brainstorming on how to
     improve VPI performance for accessing memories and arrays.

   - Agenda for the 4/30-5/1 face to face meeting
     Add accessing memories and arrays.  Switch order of compatibility
     and packed structs.

   - Chuck sent out a new compatibility doc
     Chuck would like to discuss the include file layout.  Abi asked that
     there be a 2008 compatibility mode.

5.  Reviewed items with proposals.

   - Item 1726 Clarify meaning of vpiConstantSelect
     Francoise and Jim had a long discussion on this again.
     Tied into the discussion needed on validity.

Motion to Adjourn.  JimV/Michael.  Meeting ended at 1:06pm.

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

7.  Old Business

8.  Action items

   - Ongoing review of Michael and Abi's compatibility proposal.
   - Francoise and Bassam to continue work on assignment patterns.
   - Francoise to champion adding support for typed parameters to the
     typespec diagrams.
   - Abi to champion adding support for parameterized classes.
   - Abi/JimV to champion improving the ability to compare objects.
   - Steve Dovich to determine best way to deal with issues between
     versions of the IEEE specs.
   - SV-CC to review proposal for Item 0890.
   - Michael to compose response to the Clean Scheduling Proposal.
   - All to verify their Acknowledged Mantis Items.
   - Steve to send out exact text on referring to a prior version.
   - Chas to gather a list of all SV-CC approved mantis items which have
     not been incorporated into draft 2.
   - Chas to formulate an agenda for the next SV-CC face to face meeting.


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

   - Item 1726 Clarify meaning of vpiConstantSelect
   - Item 1741 1800-2005 Section 27.50 Issues with foreach diagram


10. Next meeting
    The next SV-CC meeting will be the face to face starting on 04/30/2007.
    The next P1800 meeting will be on 05/24/2007.



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Mon Apr 30 07:55:19 2007

This archive was generated by hypermail 2.1.8 : Mon Apr 30 2007 - 07:55:22 PDT