Minutes of 02/27/2008 SV-CC Meeting. ATTENDEES 000000000000000000000000000000000000000 888887777777777777777777777777666666666 000001111100000000000000000000111110000 221112210099888876655443322111221009988 213101002121221012020212121310200212131 730629574062925180639518484173068517306 xxxxxxxxxxxxxxxx-xxx-xxxxxx-xxxxxxxxxxx Charles Dawson -xxxxxxxxxxxx--xxxxxxxxxxxxxxxxxxxxxxxx Jim Vellenga xxx-xxx-xxxx---xx--xxxxx-xxxx--xxxxxx-x Michael Rohleder xxxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxxxxxx Chuck Berking xxxxx-xxxxx-xx--xx-xxxxxxxxxxxxxx-xxxxx Bassam Tabbara xxxxxxxxxxx-xxxxxxxxxxx-xx-xx-x-xxxxxxx Francoise Martinolle xxxx-xxxxxxxx---xxxxxxxxxxx-xxxxxxxxxx- Ghassan Khoory xxxxxxxxxxxxx-----xxxxxxx-xxxxx-xxxxxxx Abigail Moorhouse x-xxx-xx-x------xxx-x--x--xxxx----xx-xx Amit Kohli xxx-xxx-------------x-----xx----------- Steve Dovich xxxxxx--------------------------------- John Shields x-xxx--x-xxxxx--xxxx------------------- Anil Arora ======================================= -----xx-x-xxxxx-xxxxxxxx-xxxxxxx-x-xxxx Ralph Duncan ---x--xx--xx-xxxxxxxxxxxxxxxx-xxx-x-xxx Andrzej Litwiniuk --------x-xxxx--xxxx------------------- Pankaj Pal ----------x-x----xx-------------------- Arjinder Vasir -----------------------x--------------- Stu Sutherland ---------------------x----------------- Gord Vreugdenhil ------------x-------------------------- Neil Korpusik ---------x----------------------------- John Havlicek 1. Reviewed Patent information - Chas reviewed the patent information which can be found at http://standards.ieee.org/board/pat/pat-slideset.ppt 2. Reviewed minutes for 02/13/2008 Chuck/Bassam. ACCEPTED 3. Approval of agenda Steve/Chuck. ACCEPTED 4. Liaisons - Chas to report on face to face meeting Slides have not been sent to reflector. Meeting was very productive. - Francoise to report on Champion issues Francoise did not have anything in particular. - No other meetings to report on. 5. Consent Agenda 6. Expedited Agenda Items - Item 1230 How to represent packed arrays of complex types in VPI John had two friendly amendments. Detail 6 on page 16 should refer to example in detail 5 on page 15. On page 14 has a type [4x3] instead of 4x2. Detail 8 second paragraph. Chas and Francoise asked a few questions which Chuck was able to answer, mainly on array nets versus packed array net. Chas asked for a friendly amendment showing a true packed array and an array of packed structs added to note 1. Francoise agreed. Francoise/Michael. PASSED (unanimous) as amended. Chuck to update the proposal. 7. New business - Items on which there is agreement in principle John recapped what we discussed last week: Reviewed last 5 weeks of discussions which we had. Reviewed terminology and past proposals. John made a new proposal. The high level idea is that the ability to track the birth and life of an object, callbacks, ..etc is a workable concept. Having a recyclable object identifier is an efficient way to track objects. The proposal has referential integrity until the object is dies (garbage collected). We agreed that this proposal meets the needs of the other proposals, and it removes the need for a callback with when the HDL last reference is gone, or the need for Unknown for vpiValid. Proposal: Need the ability to look at the current state of the data. Need to be able to track the dynamic data. Need to be able to be accurate and efficient. Support for the packet tracking use model. Support for the difficult debugging problem. Referential integrity: handle to an object needed to be usable across the life of the object. Does not preclude a handle being a first class object for the simulation, or a transient model. Avoiding logging data more than once, so we created a unique identifier for the dynamic object. Identifier has to be efficient, or won't scale for small objects. Minimum 64 bits. ID is subject to reuse when the object dies. Global recycling count. Can use as a tuple with the object identifier results in a UID for the object. Logistics: We need to get things in writing in the first half of March. John will have something on the action items by next week. Key terminology and the proposal in text by next week. John thinks he needs to write up some rational so that people can get a better understanding of what we are trying to do. - SV-AC issues reported by John Havlicek Chas will ask for more time at P1800 meeting. Depending on the P1800 response, we will set our schedule. - Others? Motion to adjourn: Chuck/Micheal. Meeting ended at 1:03pm 8. Reviewed items with proposals 9. Reviewed SV-CC items with proposals (Straw poll only) 10. Old Business 11. Action items - Francoise and Bassam to continue work on assignment patterns. - Francoise and Bassam to figure out what should happen when you get the size of a string constant. - Chas to update Item 1570. - Chas to ask the editor about Item 0417. - Steve to write a proposal for dealing with the inconsistencies with the protection properties. - Chas to talk with editor on re-arranging the VPI that is outside of the VPI sections. - Bassam, JimV, and Lisa Piper to work on issues found in Item 1503. - Chas to ask the editor for the framemaker for the Data Read API. - Chas to implement a "consent agenda" and an "Expedited Proposals" in agenda. - Chas to add an "Agenda Approval" to the agenda. - Chas to schedule another Data Read API meeting after DVCon. - Bassam to implement the friendly amendment to Item 1599. - Chas to ask John Havlicek to join the SV-CC meeting when we discuss SV-AC issues. - Chas to ask the SV-AC to fix the #defines in proposal for Item 2005. - Francoise to bring up the issues we found with Item 2250 at Champions meeting. - Chuck to update proposal for Item 1230 with three friendly amendments. 12. Items for consideration at the next meeting (they already have proposals) - Item 2218 Clarify meaning of vpi_compare_objects() - Item 2216 Details missing from VPI Generates object diagram - Item 2143 How should VPI handle index expressions with side effects? - Item 2054 Draft 3A, Section 40 - Deprecate Data Read API - Item 2094 Need to extend VPI to handle class specializations - Item 1599 The assertion API and VPI sections need changes as per mantis #805 - Item 2262 Missing definition in vpi_user.h for vpiIsProtected - Item 1688 Performance of VPI access to memories and MDAs is inadequate - Item 0555 31.1 Introduction not needed in context of the larger document - Item 0556 31.2 Beginning of this section not needed in larger context of spec - Item 0557 31.3.1 specific references to objects should be removed - Item 0558 31.3.3 rename section to "Access availability" - Item 0560 31.4.1 & 31.4.2.1 Overloading vpi_handle() is a bad idea - Item 0561 31.4.2 vpi_free_object() should be explicitly referenced here - Item 0562 31.5 needless restriction on traverse object creation - poor terminology - Item 0563 31.5 diagram in figure 31-18 needs to be redrawn - Item 0565 31.6 remove first paragraph of this section - Item 0570 31.8.1 Need prototype for vpi_load_extension() - Item 0571 31.8.1 unnecessary complication added for vpi_close() - Item 0572 31.8 make use of the term 'user' - Item 0580 31.8.4 section is not necessary and colloquial - Item 0583 31.8.4.2 terminology first defined in a footnote? - Item 0584 31.8.4.2 implies that vpi_goto() creates new handle - Item 0593 31.12 Routines should be in table format - Item 2146 Data read API description references wrong header file - Item 2148 Unclear statement about error handling after calling vpi_unload() 13. Next meeting The next SV-CC meeting will be on 03/23/2008. The next P1800 meeting will be on 02/28/2008. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Feb 27 13:26:45 2008
This archive was generated by hypermail 2.1.8 : Wed Feb 27 2008 - 13:27:08 PST