SV-BC Committee Meeting Date: Monday, September 11, 2006 Time: 09:00am-11:00am PDT 11 Day 14 00 Month 98 00 Year 66 aa Matt Maidment - Intel aa Brad Pierce - Synopsys aa Shalom Bresticker - Intel no aa Cliff Cummings - Sunburst Design a- Surrendra Dudani - Synopsys aa Mark Hartoog - Synopsys aa Francoise Martinolle - Cadence aa Karen Pieper - Synopsys aa Dave Rich - Mentor Graphics aa Steven Sharp - Cadence aa Gordon Vreugdenhil - Mentor Graphics -a Doug Warmke - Mentor Graphics aa Stu Sutherland - Sutherland HDL aa Logie Ramachandran - Synopsys a- Don Mills - LCDM Engineering -a Rishiyur Nikhil - Bluespec aa Heath Chambers - Consultant/Trainer Agenda + Review IEEE patent policy http://standards.ieee.org/board/pat/pat-slideset.ppt It was reviewed. + Review Minutes of Previous Meeting http://www.eda.org/sv-bc/minutes/sv-bc_06_08_14.txt Cliff moves to approve minutes. Gord seconds. No opposed. No abstain. Motion passes. + 1800 Process Updates From champions: For any enhancements, initiating committees must notify other, affected committees of their work, especially if the enhancements include keywords or system functions. + SVDB 1323 http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0001323 Implementations have diverged on this issue and Gord asked that the committee make every effort to resolve this as soon as possible. Chaining of imports Hierarchical references to identifiers in imported packages AI: Dave open new issue to address hierarchical references of imported identifiers. Copy Stu's bug note from 1323 to new issue. Dave updated the proposal for 1323 to address only package import. Gord moves to accept the proposal for 1323. Francoise seconds. Opposed: Mark - chaining of imports makes language more powerful and flexible. Makes resuse of IP more difficult. Logie - chaining of imports makes language more powerful and flexible. Makes resuse of IP more difficult. Brad - not backward compatible with existing implementations. Adding a restriction to the LRM that was not there before. Surrendra - not backward compatible with existing implementations. Stu - not backward compatible with existing implementations. restriction that's not needed Don - as a user, when package imported, seems natural for other identifiers visible to that package are visible Karen - not backward compatible with existing implementations. For: Gord, Francoise, Cliff, Shalom, Steven, Dave Abstain: Heath Motion Fails. Feedback: committee members interested in both chaining and no chaining capabilities. With both capabilities explicitly defined in the LRM, committee members would be willing to approve one as the default. Adding an export capability to packages may come closest to explictly enabling chaining. AI: Gord, Mark, Stu and Don to pursue proposal to enable package chaining. Goal is to bring a proposal to Sep 25 SV-BC meeting. AI: Gord to notify SV-EC about this activity. + SV-AC 1549 In his post to the SV-BC reflector http://www.eda.org/sv-bc/hm/5050.html Brad asked that this committee review SV-AC 1549. This agenda item was not reached. It will be carried forward to future agendas until it is addressed. + 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: September 25 Action Items Complete 08/14/2006 Shalom to attach a more formal proposal to SVDB 1119 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. 09/11/2006 Dave open new issue to address hierarchical references of imported identifiers. Copy Stu's bug note from 1323 to new issue. 09/11/2006 Gord, Mark, Stu and Don pursue proposal to enable package chaining for Sep 25 SV-BC meeting. 09/11/2006 Gord notify SV-EC about effort to enable package chaining.