SV-BC Committee Meeting Date: Monday, October 09, 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 0211 Day 9514 1000 Month 0998 0000 Year 6666 aaaa Matt Maidment - Intel aaaa Brad Pierce - Synopsys aaaa Shalom Bresticker - Intel aaaa Cliff Cummings - Sunburst Design aaa- Surrendra Dudani - Synopsys aaaa Mark Hartoog - Synopsys -aaa Francoise Martinolle - Cadence aaaa Karen Pieper - Synopsys aaaa Dave Rich - Mentor Graphics aaaa Steven Sharp - Cadence aaaa Gordon Vreugdenhil - Mentor Graphics aa-a Doug Warmke - Mentor Graphics aaaa Stu Sutherland - Sutherland HDL aaaa Logie Ramachandran - Synopsys aaa- 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_09_25.txt Shalom moves to accept the minutes as posted. Gord seconds. No opposed. No abstain. Motion passes. + E-mail Vote Results Pass: 967, 982, 1337, 1493, 1496, 1529, 1534, 1538, 1539, 1540 1119 Brad: "missing end, & not backward compatible" Mark: Not backward compatible Shalom fixed missing end. Stu moves to accept proposal, amended with replacement of "However, m" with "M". Shalom seconds. For: Stu, Shalom, Cliff, Steve, Gord, Doug, Logie, Don, Dave Opposed: Brad: Not backward compatible, Verilog users need means to do this. Only SystemVerilog has `" capability. Legacy verilog code will continue to rely on tools substituting macro arguments in strings. Karen: Not backward compatible, Verilog users need means to do this. Only SystemVerilog has `" capability. Legacy verilog code will continue to rely on tools substituting macro arguments in strings. Mark: Not backward compatible, Verilog users need means to do this. Only SystemVerilog has `" capability. Legacy verilog code will continue to rely on tools substituting macro arguments in strings. Abstain: Surrendra: Needs more time to determine scope of impact to backward compatibility. Motion Passes. AI: shalom update the proposal for 1119 per amendment. 1209 Brad: Missing bolding on keywords, 'struct' instead of 'structure', and wondering why it says both 'aggregate parameter' and 'parameter aggregate'. Shalom updated proposal to address Brad's comments. Brad moves to accept proposal. Stu seconds. No opposed. No abstain. Motion passes. AI: Shalom: add an additional mantis to enable parameters with dynamic data types 1341 Gord: There has been some additional discussion here about the relationship between `resetall, `begin_keywords, and single/multi unit compilation semantics. I think that I'd like to have a bit more discussion on this yet. Gord would like to clearly specify result of reaching end of a compilation unit before reaching `end_keywords directive. AI: Gord to file SVDB entry to specify behavior of `being/`end directives when no `end is encountered before end of compilation unit. Steves moves to accept proposal. Cliff seconds. No opposed. No abstain. Motion passes. 1554 Shalom prefers wording in Mantis Cliff suggested alternate wording Dave suggested alternate wording Cliff's suggestion was generally liked. A minor modification was further incorporated: It shall be legal to call any of these query functions within a constant expression if all three of the following conditions are true: (1) the call would be legal in an expression, (2) the first argument is a fixed-size type or is an expression of some fixed-size type, and (3) any optional dimension expression is a constant expression. AI: Brad enhance proposal to prevent circularity of expressions. (address use or non-use of hierarchical references). + 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. + Next Meeting Date: October 23 Action Items Dropped 04/24/2006 Matt identify any other threads of major issues Complete 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. 07/10/2006 Matt move Gord's document to 1268 09/11/2006 Dave open new issue to address hierarchical references of imported identifiers. Copy Stu's bug note from 1323 to new issue. This is now SVDB 1583. 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 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 Shalom: update the proposal for 1119 per amendment. 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