SV-BC Errata Committee Meeting Date: Monday, July 10, 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 1102021210000 Day 0952840736957 0000000000011 Month 7665544332121 0000000000000 Year 6666666666655 aaaaaa-aaaaaa Matt Maidment - Intel aaaaaaaaaaaaa Brad Pierce - Synopsys aaaaaaaaaaaaa Shalom Bresticker - Intel (off at 10am) aaaaa--aaaaaa Cliff Cummings - Sunburst Design ---aaaaa-a-aa Surrendra Dudani - Synopsys aaaaaaaaaaaaa Mark Hartoog - Synopsys aaaaaaaaaaa-a Francoise Martinolle - Cadence aaaaaaaaaaaaa Karen Pieper - Synopsys -aaaaaaaaaaaa Dave Rich - Mentor Graphics (15 minutes) a-aa-aaaa-aaa Steven Sharp - Cadence -aaaaa-aaaaaa Gordon Vreugdenhil - Mentor Graphics --a-aaaaaaaaa Doug Warmke - Mentor Graphics (on and off) a-aa---aaaaa- Stu Sutherland - Sutherland HDL (til 10:15) aa--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 a------------ 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.verilog.org/sv-bc/minutes/sv-bc_06_06_19.txt Dave moves to accept the minutes as posted. Cliff seconds. No opposed. No abstain. Motion passes. + Name resolution discussion Mark: What is interfaceport. a hierarchical reference or is it something else? All: what's the difference? It's a different scope Dave: It's a matter of what is available at compile time Dave: Suggests defining rules for accessing interface port items Brad: no way to specialize an interface, except at interface instantiation this necessitates postponing resolution to elaboration Mark: Users want to refer to a parameter through an interface port. Conclusions for this round of discussion: 1) Fix 1043 separately. Should carry forward. 2) Higher priority: Extension of clause 12 for 1800 Contributing constructs interface ports virtual interfaces structs (including declared by type parameters) built-in type methods (enum & arrays, including declared by type parameters) class methods (including declared by type parameters) class members unions hierarchical name references into packages? named block inside unnamed block Initially covered named blocks (generate, begin-end, task/function) modules Next step is to hash it out in sub-committee; stalled until August when Gord returns from vacation. AI: Matt move Gord's document to 1268 AI: Steve add bugnote to 1043 about specifics for resolution + Cliff asked about potential syntax for 0-1 wildcard. Steve replied that the real issue is how to tackle X-optimism. Steve suggests that one issue to tackle is the simulation behavior for "worst case" where an if expression is unknown. Are tasks and functions called? Which/are display/print system tasks are called? Perhaps restricting the if statement to only variable assignments would be a way to do it. Cliff now off further considering the issues. + 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, 1336 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 + Proposed Next Meeting Date: July 31 Action Items Complete 06/05/2006 Stu add bugnote to SVDB 1323 explaining use-case to justify change 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 proposal for SVDB 1380 with additional note to editor. 06/19/2006 Matt cut-and-paste statement about "%m" as additional info for SVDB 672. 06/05/2006 Matt elevate questions about priority and feasibility of PAR tasks to 1800 Johny agreed. Pending PAR approval 06/19/2006 Matt send email ballot with 1 week for response 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