SV-BC Errata Committee Meeting Date: Monday, June 19, 2006 Time: 09:00am-11:00am PDT 102021210000 Day 952840736957 000000000011 Month 665544332121 000000000000 Year 666666666655 aaaaa-aaaaaa Matt Maidment - Intel aaaaaaaaaaaa Brad Pierce - Synopsys aaaaaaaaaaaa Shalom Bresticker - Intel aaaa--aaaaaa Cliff Cummings - Sunburst Design --aaaaa-a-aa Surrendra Dudani - Synopsys aaaaaaaaaaaa Mark Hartoog - Synopsys aaaaaaaaaa-a Francoise Martinolle - Cadence aaaaaaaaaaaa Karen Pieper - Synopsys aaaaaaaaaaaa Dave Rich - Mentor Graphics -aa-aaaa-aaa Steven Sharp - Cadence aaaaa-aaaaaa Gordon Vreugdenhil - Mentor Graphics -a-aaaaaaaaa Doug Warmke - Mentor Graphics -aa---aaaaa- Stu Sutherland - Sutherland HDL a--a--a-aa-- Logie Ramachandran - Synopsys -a----a--aa- Don Mills - LCDM Engineering ----------a- Bill Paulsen - Cadence --------a-a- Rishiyur Nikhil - Bluespec --------aa-- Chris Spear - Synopsys --------aaaa Dan Jacobi - Intel Open Item Future Meeting schedule. All requested meetings remain in sync with SV-EC and not occur DAC week. July meetings: 10th & 31st. Meeting will then occur on their regular bi-weekly basis starting August 14th. AI: Matt send mail to Mehdi to reschedule SV-EC meeting. Agenda +Review IEEE patent policy http://standards.ieee.org/board/pat/pat-slideset.ppt Reviewed by the sv-bc. + Review Minutes of Previous Meeting http://www.eda-stds.org/sv-bc/minutes/sv-bc_06_06_05.txt Karen moves to accept. Gord seconds No opposed. No abstain. Motion passes. + Resolve E-mail ballot issues (Reminder: votes due by Midnight PDT, June 16) Issue Status 515 Pass 969 Pass 981 Pass 1005 Pass 1137 Pass 1149 Pass 1154 Pass 1216 Fail 1227 Pass 1332 Pass 1377 Pass 1378 Fail 1380 Fail 1216 http://www.verilog.org/sv-bc/hm/4664.html AI: Brad update proposal for SVDB 1216 per Shalom's feedback 1378 http://www.verilog.org/sv-bc/hm/4634.html Brad moves to accept proposal with friendly amendment to change quotation marks to apostrophes in a.6.7.1 Gord seconds. No opposed. No abstain. Motion passes. AI: Brad to make quotation mark change to proposal for SVDB 1378. 1380 http://www.verilog.org/sv-bc/hm/4664.html Shalom proposes friendly amendment to add note to editor to change apostrophe in middle of line as well as at beginning of line. Brad seconds. No opposed. No abstain. Motion passes. AI: Brad update proposal for SVDB 1380 with additional note to editor. + Other topics a) SVDB 1290, 219 1) What should be allowed? 2) What guarantees is a simulation required to give? 3) Are there any interactions with 1364 issues Fork-join none within functions; Can a thread created from a function introduce a delay? General agreement for allowing thread creation with delay from functions but need restrictions for constant functions, functions called from combinational processes (continuous assigns and always_*) and packages. When and how many threads should be predictable. AI: Dave to draw up some guidelines about thread creation from functions or SV-BC to vote/capture consensus and pass along to other committees. b) In terms of i/o (and VCD), the main questions involve how to bound the problem since, assumbably, no one wants to deal with dynamic types in those domains. AI: Francoise check with SV-CC regariding suitability of data read API to address debugging of "dynamic data" in lieu of vcd extensions. AI: Gord raise the issue of support of dynamic data in vcd to SV-EC. Some favor support for all static data types including unpacked arrays. Response from SV-EC & SV-CC will shape direction of efforts to address vcd-related issues. c) What is "%m" supposed to do for parameterized class specializations. Implementations certainly have diverged on this and we really should get something definitive stated. (See SVDB 672) Trying to do the dynamic path name through %m is not a good idea. Too expensive to implement and best left for debugging tools. Any proposal on this topic should cover paths to the elaboration of the routine, not the dynamic call path. AI: Matt cut-and-paste statement about "%m" as additional info for SVDB 672. + 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 Primary Owner: Steven Participants: Steven, Gord, Mark, Francoise Enumerated Types Issues: 916, 917, 1429, 1483 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, 1208, 1292, 1333, 1338, 1339, 1341, 1397, 1478 Primary Owner: Shalom Next e-mail vote: 1030, 1108, 1154, 1283, 1430, 1475 AI: Matt send email ballot with 1 week for response + Next Meeting Date: July 10th Action Items Complete 05/22/2006 Brad search for non-local or "non local" in LRM. File another issue to correct if found. Shalom verified no such instances are in LRM. (http://www.eda-stds.org/sv-bc/hm/4731.html) 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/05/2006 Stu add bugnote to SVDB 1323 explaining use-case to justify change 06/05/2006 Matt elevate questions about priority and feasibility of PAR tasks to 1800 06/19/2006 Brad update proposal for SVDB 1216 per Shalom's feedback 06/19/2006 Brad to make quotation mark change to proposal for SVDB 1378. 06/19/2006 Brad update to update proposal for SVDB 1380 with additional note to editor. 06/19/2006 Dave to draw up some guidelines about thread creation from functions or 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. 06/19/2006 Matt cut-and-paste statement about "%m" as additional info for SVDB 672. 06/19/2006 Matt send email ballot with 1 week for response