Minutes of 0/13/2006 SV-CC Meeting. ATTENDEES 000 666 000 988 131 306 xxx Charles Dawson xxx Ralph Duncan xxx Jim Vellenga xxx Andrzej Litwiniuk xxx Abigail Moorhouse x-x Michael Rohleder xxx Chuck Berking xxx Bassam Tabbara xxx Francoise Martinolle -xx Amit Kohli xx- Ghassan Khoory --- Steven Dovich --- Stu Sutherland --- Ankur Kuchlous --- Nasim Hussain --- Sachchidananda Patel 1. Reviewed Patent information. - Chas reviewed the patent information. 2. Reviewed minutes of the 08/30/2006 Meeting. - Ralph/JimV. ACCEPTED (unanimous) 3. Liaisons - Francoise reported that there was a Champions meeting where they reviewed the passed items. - AC committee has one item (1549) that the Champions would like the SV-CC to review. Proposal will add a new keyword. Should it be generalized to work beyond properties of sequences? BC and EC committee were also asked to review. JimV asked if we are going to have to change access to assertions? Francoise thought that it probably would. We should ask Bassam to comment on this proposal (was not at SV-CC meeting when this discussion occurred - joined later). - Francoise asked if there is a mantis item for issues with typed parameters. Yes, it is Item 1311. - There has been some controversy in SV-BC on import clauses and packages. LRM is not clear and has diverging implementations. May have an impact on our data model. Some people thinks it works just like in VHDL, and others don't. Chaining of import statements makes it hard to hide things. Can get redundant symbols. Can you have OOMRs (Out Of Module References) to them? Some people think so. Francoise thinks that including a package does not create a declaration in the scope for objects in the package, so no OOMR. - No one reported on other meetings 4. New business - vpiName vs. vpiFullName vs. vpiDecompile discussion on members of structs When you have a member select used in an expression. What should it's name be? We think the name should be just the member name. The decompile should be struct and member name. The full name would include it's entire scope. How will handle by name work? Should a struct be a scope? Abi and Chuck don't think so. How should vpiDecompile work for OOMRs? For simple expressions, just the local name is okay. For complex expression? Good topic for face to face meeting. Chuck to file mantis item(s) for this discussion. - Michael asked about interoperability issue. Charles thinks it will be discussed at the next P1800 meeting. 5. Reviewed of items with proposals. 6. Reviewed SV-CC items with proposals (Straw poll only). - Item 1570 Clarify legality of 'integer' and 'time' as DPI parameter types Ralph described the change since last time. Proposal has been simplified. Michael/Abi. PASSED (unanimous) - Item 1579 Unused vpiMultiArray declaration in vpi_user.h Postponed until next meeting. Ralph/Abi. Meeting ended at 1:00pm. 7. Old Business 8. Action items - JimV to look into other things which can have size changes as discussed in 0985. - Chas to send everyone the frame docs for the diagrams. - Chuck to write a document that describes the possible solutions for the compatibility issues, and they're pros and cons. - Francoise and Bassam to continue work on assignment patterns. - Chas to send Michael a copy of the PAR proposal. - Francoise to send VCD recommendation to SV-BC. - Chas to ask P1800 how a face-to-face meeting would effect voting rights. - Chuck to file mantis item(s) for the vpiName discussion. 9. Items for consideration at the next meeting (they already have proposals): - Item 1579 Unused vpiMultiArray declaration in vpi_user.h 10. Next meeting The next SV-CC meeting will be on 09/27/2006. The next P1800 meeting will be on 09/21/2006. -- Charles Dawson Senior Engineering Manager NC-Verilog Team Cadence Design Systems, Inc. 270 Billerica Road Chelmsford, MA 01824 (978) 262 - 6273 chas@cadence.comReceived on Wed Sep 13 12:25:34 2006
This archive was generated by hypermail 2.1.8 : Wed Sep 13 2006 - 12:25:57 PDT