SV-BC Errata Committee Meeting Date: Monday, August 14, 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 1 Day 4 0 Month 8 0 Year 6 a Matt Maidment - Intel a Brad Pierce - Synopsys a Shalom Bresticker - Intel a Cliff Cummings - Sunburst Design - Surrendra Dudani - Synopsys a Mark Hartoog - Synopsys a Francoise Martinolle - Cadence a Karen Pieper - Synopsys a Dave Rich - Mentor Graphics a Steven Sharp - Cadence a Gordon Vreugdenhil - Mentor Graphics a Doug Warmke - Mentor Graphics a Stu Sutherland - Sutherland HDL a Logie Ramachandran - Synopsys - Don Mills - LCDM Engineering a Rishiyur Nikhil - Bluespec a Heath Chambers - Consultant/Trainer Agenda + Review IEEE patent policy http://standards.ieee.org/board/pat/pat-slideset.ppt + Review Minutes of Previous Meeting http://www.verilog.org/sv-bc/minutes/sv-bc_06_07_31.txt Dave moves to accept the minutes. Karen seconds. No opposed. No abstain. Motion passes. + PAR Update The latest 1800 PAR was recently approved by the IEEE: http://standards.ieee.org/board/nes/projects/1800.pdf "The new revision of the standard will include resolutions and clarifications to Errata and critical enhancements that will enable successful usage of the hardware design and verification language. Furthermore, and as SystemVerilog is a superset of Verilog, the new revision will merge with Verilog 1364-2005 standard to ensure a single reference manual for users and EDA vendors alike. The new standard will also enable interoperability with existing languages such as VHDL and SystemC, as well as integration with Analog Mixed Signal (AMS)." o Karen will provide update on processes Enhancements: "modifications should be well contained." Up to committees to decide scope. If committee thinks scope is too large, elevate to 1800 committee. Approval process similar to previous PAR. Resolved to Champions to 1800 Committee to editor to review state to closed. Voting privileges reset as of the Aug 14 meeting. Champions meetings to start in approximately 2 weeks. Will go to 1800 after that. 1800 committee still being organized, process may be delayed until organization is set. Dave moves: "1800 Committee needs to provide mechanism for communicating changes in a timely manner." Shalom seconds. Opposed: Stu (information is already available & maintaining a list diverts effort from addressing next LRM). Abstain: Brad Dave volunteers to work on solution. AI: Matt to forward this request to 1800 and include Dave's name if they are looking for participation to resolve it. o Brad will provide update on VHDL efforts Brad chartered to figure out scope. Suggestion: Limit interoperability to module port boundaries. Big issue: co-simulation scheduling. Other issues: value resolution, configurations Consider limiting scope based on PAR timeframe Gord suggests 1-2 day face-to-face meeting to define scope Dave suggests identifying a user champion, or collect a user-driven set of requirements to scope the work. Stu suggests forming a task force or preferrably sub-committee, to identify what should be addressed, what can be addressed in timeframe of PAR and bring back to 1800 for review. This task force or committee should be distinct from EC, BC, AC and CC. Participation preferrably includes participants from all other committees. Suggestion to request donation from any vendor with real implementation to seed the effort. Francoise asks whether this effort need to account for 200X LRM? + 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. o SVDB 1119 (http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0001119) Initial proposal on the reflector: http://www.eda.org/sv-bc/hm/4946.html AI: Shalom to attach a more formal proposal to SVDB 1119 and it will be included in a future e-mail vote. o SVDB 1557 (http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0001557) Dave moves to close this issue as '? detracts from the readability of the language. Steven seconds. Opposed: Brad orthogonality; Shalom simplifies BNF. Abstain: No. Motion passes. o SVDB 1401 (http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0001401) Tabled until the next meeting. o Brad identified the following issues as potentials for an e-mail vote: http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0000967 http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0000982 http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0001493 http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0001529 http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0001534 http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0001538 http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0001539 http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0001540 http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0001554 No other issues suitable for email vote. Any one who votes no can force issue to be voted on at next meeting. + Next Meeting Date: September 11 Action Items Complete Pending 01/09/2006 Shalom add example for issue 1254 describing situation for rule 3 03/13/2006 Matt Open up SV-BC Issue requesting an index for P1800 03/27/2006 Cliff post examples demonstrating the need for 0-1 wildcard to justify further action on SVDB 99 04/10/2006 Steven to create proposal for SVDB 1386 04/10/2006 Steven to create proposal for SVDB 1078 04/24/2006 Matt identify any other threads of major issues 05/22/2006 Gord Second issue regarding scoping & forward visibility in $unit. 05/22/2006 Gord Enter mantis item & deliver proposal to address name resolution issues 05/22/2006 Steven & Mark Review Gord's name resolution proposal. 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 Matt move Gord's document to 1268 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 this request to 1800 and include Dave's name if they are looking for participation to resolve it. 08/14/2006 Shalom to attach a more formal proposal to SVDB 1119