SV-BC Committee Meeting Date: Monday, October 23, 2006 Time: 09:00am-11:00am PDT Toll Free Dial In Number: (888)635-9997 International Access/Caller Paid Dial In Number: (763)315-6815 PARTICIPANT CODE: 53904 20211 Day 39514 11000 Month 00998 00000 Year 66666 aaaaa Matt Maidment - Intel aaaaa Brad Pierce - Synopsys aaaaa Shalom Bresticker - Intel -aaaa Cliff Cummings - Sunburst Design aaaa- Surrendra Dudani - Synopsys aaaaa Mark Hartoog - Synopsys a-aaa Francoise Martinolle - Cadence aaaaa Karen Pieper - Synopsys aaaaa Dave Rich - Mentor Graphics -aaaa Steven Sharp - Cadence aaaaa Gordon Vreugdenhil - Mentor Graphics -aa-a Doug Warmke - Mentor Graphics aaaaa Stu Sutherland - Sutherland HDL aaaaa Logie Ramachandran - Synopsys aaaa- Don Mills - LCDM Engineering ----a Rishiyur Nikhil - Bluespec -aaaa Heath Chambers - Consultant/Trainer Agenda + Review IEEE patent policy http://standards.ieee.org/board/pat/pat-slideset.ppt Reviewed. + Review Minutes of Previous Meeting http://www.eda.org/sv-bc/minutes/sv-bc_06_10_09.txt Gord moves to accept the minutes as updated. Stu seconds. No Opposed. No abstain. Motion passes. Open: Gord notified the SV-BC that the SV-EC is tentatively planning a face-to-face meeting for November 6. The SV-BC needs to consider rescheduling its November 6 meeting. The first suggestion was an abbreviated meeting prior to the start of the November 6 SV-EC meeting. Another suggestion is to reschedule the SV-BC meeting for another day. A final decision will be made pending a final schedule from the SV-EC. + Issues for Voting SVDB 1192, 1193 http://www.eda.org/svdb/bug_view_page.php?bug_id=0001192 http://www.eda.org/svdb/bug_view_page.php?bug_id=0001193 Shalom moves to resolve SVDB 1192 & 1193 in favor of new issue 1643. Stu Seconds. No opposed. No abstain. Motion passes. SVDB 1462 (http://www.eda.org/svdb/bug_view_page.php?bug_id=0001462) Gord moves to accept proposal in 1462. Logie seconds. No opposed. No abstain. Motion passes. SVDB 1607 (http://www.eda.org/svdb/bug_view_page.php?bug_id=0001607) A lot of discussion around the question of whether or not a wildcard package import can finalize a forward type reference that makes an im. Because this is a subtle feature and because the sentence is very general, it was requested that examples be provide and potentially additional clarification be added. 2 issues were ultimately identified: 1) Can a forward typedef be finalized from an implicit (wildcard) package import 2) Can finalizing forward typedef in scope occur before and/or after usage, especially in the case that Matt identified: $unit. AI: Dave will add text and legal and illegal examples to clarify issues covered by SVDB 1607 AI: Matt send example of use of forward typedef. The SV-BC agreed that answering the second question is not part of 1607 as this is a much broader issue than this issue of the interaction of packages and typedefs. SVDB 1609 (http://www.eda.org/svdb/bug_view_page.php?bug_id=0001609) Dave moves to transfer this to SV-EC as topic for SV-EC charter. Brad seconds. No opposed. No abstain. Motion passes. AI: Brad move SVDB 1609 to SV-EC SVDB 1625 (http://www.eda.org/svdb/bug_view_page.php?bug_id=0001625) Brad moves to accept proposal. Mark seconds. No opposed. No abstain. Motion passes. + Macro Discussion Some high-level discussion took place. Below is a very terse summary. Many do not want to see the macro language expanded because widescale use of complex macros impacts (negatively) debugging and the VPI. Some also raised that as the macro language grows, it could become more confusing to understand when to use it and when to use generate. Many would like to see the rest of the language enhanced instead. The counter-argument is that a more powerful macro language may resolve more language across many features, others again countered that widescale use would be a disservice to the lanague. There may be support for simpler enhancements. Resistance started to grow with the mention of a varargs-type of feature. + Issue Review Process: Identify subset of issues to focus committee effort Assign owners for the issues Owners bring issues to vote when draft of proposal complete Rebuttal to issues should come in the form of specific changes to proposal Guidelines for issues: - Group would prefer not to address issues that complicate merging of the LRMs or require edits to both specs. Group would prefer to address more isolated errata until next PAR is set. - Try to clarify intent of some issues even if no formal resolution. This would be useful for keeping implementations consistent. - Major Severity will be used to identify issues that if not addressed will lead to visibly different implementations. - Group will use severity to quantify impact of change. Issues will be addressed in order of severity. - Priority will indicate issue's development progress. Increase in priority indicates increased progress to proposal and vote. 'Immediate' priority indicates issue is ready for a vote. - Individuals will indicate ownership of resolution by adding themselves to the 'assigned to' field. Karen will help anyone who cannot update an issue. - Individual members can increase the severity of an issue but the group must agree to decrease severity. - Status Filed: Assigned, Resolved & Closed are key states. Issue Themes Namespaces Issues: 30, 1213, 1214, 1220 Primary Owner: Francoise Participants: Gord, Francoise, Mark, cc: Shalom, cc: Karen I/O Errata/Clarification Issues: 672, 1078, 1386: Steven ; 988: Gord Primary Owner: Steven Participants: Steven, Gord, Mark, Francoise Enumerated Types Issues: 916, 917, 1429 Primary Owner: Matt Configurations Issues: 986 (see bugnote for related items) Primary Owner: TBD (proposed as Cliff but he was not present) Scheduling Issues: 1290, 219 Primary Owner: TBD (Gord; after first round of issues are addressed) Compiler Directives Issues: 1052, 1053, 1084, 1119, 1202, 1292, 1333, 1338, 1339, 1341 Primary Owner: Shalom Name Resolution Primary Owner: Gord Participants: Francoise, Steven, Mark, Shalom. + Proposed Next Meeting Date: November 6 Action Items Complete 10/09/2006 Shalom: update the proposal for 1119 per amendment. 03/13/2006 Matt Open up SV-BC Issue requesting an index for P1800 Pending 01/09/2006 Shalom add example for issue 1254 describing situation for rule 3 03/27/2006 Cliff post examples demonstrating the need for 0-1 wildcard to justify further action on SVDB 99 Other ideas: elsex, defaultx, ifx, alwaysx, initialx, Question: what about X expression in index of Vector or array expressions (a[i] where i === 'X). Cliff to pursue further action. 04/10/2006 Steven to create proposal for SVDB 1386 04/10/2006 Steven to create proposal for SVDB 1078 05/22/2006 Gord file issue regarding scoping & forward visibility in $unit. 06/19/2006 Dave to draw up some guidelines about thread creation from functions for SV-BC to vote/capture consensus and pass along to other committees. 06/19/2006 Gord raise the issue of support of dynamic data in vcd to SV-EC. 06/19/2006 Francoise check with SV-CC regariding suitability of data read API to address debugging of "dynamic data" in lieu of vcd extensions. 07/10/2006 Steve add bugnote to 1043 about specifics for resolution 07/31/2006 Steve add bug note to 1481 with details for a clearer proposal 08/14/2006 Matt to forward request for timely updates to 1800 standard to 1800 committee and offer Dave's name if seeking participants to enable. 09/25/2006 Matt add SVDB entry to request capability to packages: import/export & non-exported (local) package declarations. 09/25/2006 Matt send feedback to sv-bc/sv-ac regarding SVDB 1601 10/09/2006 Gord/Dave: draft proposal to resolve SVDB 1484 10/09/2006 Brad: enhance 1554 proposal to prevent circularity of expressions (address use or non-use of hierarchical references). 10/09/2006 Shalom: add an additional mantis to enable parameters with dynamic data types 10/23/2006 Dave will add text and legal and illegal examples to clarify issues covered by SVDB 1607 10/23/2006 Matt send example of use of forward typedef. 10/23/2006 Brad move SVDB 1609 to SV-EC