Minutes of the February 6, 2006 SV-BC Errata Committee Meeting 0000 Day 6957 0011 Month 2121 0000 Year 6655 aaaa Matt Maidment - Intel aaaa Brad Pierce - Synopsys aaaa Shalom Bresticker - Intel aaaa Cliff Cummings - Sunburst Design a-aa Surrendra Dudani - Synopsys aaaa Mark Hartoog - Synopsys aaaa Dan Jacobi - Intel aa-a Francoise Martinolle - Cadence aaaa Karen Pieper - Synopsys aaaa Dave Rich - Mentor Graphics -aaa Steven Sharp - Cadence aaaa Gordon Vreugdenhil - Mentor Graphics aaaa Doug Warmke - Mentor Graphics -aa- Don Mills - LCDM Engineering aaa- Stu Sutherland - Sutherland HDL --a- Bill Paulsen - Cadence a-a- Rishiyur Nikhil - Bluespec aa-- Chris Spear - Synopsys aa-- Logie Ramachandran - Synopsys 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_01_09.txt Dan proposes to accept the minutes as posted. Dave seconds. No opposed. No abstain. Motion Passes. + P1800 Committee Meeting Update Per Karen (http://www.eda.org/sv-bc/hm/3792.html) the P1800 Committee has requested feedback from the sub-committees on: 1) Should 1364 & 1800 be merged? Francoise: Yes. Sooner than later. Need enough time to complete. Doug: (1) Should not expect it to be perfect. Keep same faults and not introduce new ones. (2) Go for big items, not small ones. Gord: If we don't merge soon, will become more difficult later to merge & to deal with issues/interpretations Dave: Some sections come for free, some sections need to be merged for clarity Nikhil: Believe that merged LRM very practical Dave: Users quote LRM on bug filing. It is an important document for users. Brad, Karen, Cliff, Nikhil support inclusion of enhancements in the next PAR. Gord strongly supports providing clarification of ambiguities in current LRM. He also supports addressing complex clarifications, even if the merge does not go through. Gord supports clarifications over performing a merge. Doug supports clarifications and merge equally, both with more importance than enhancements. Shalom: Users have problems due to language limitations that require enhancements to solve them. Clarifications are important, but such enhancements are no less important. Gord: Clarifications help users with combatibility-- which is important, too. 2) If 1364 & 1800 should be merged, when should it be done? Straw poll indicated: If editor is funded SV-BC would like to receive first draft by June 1, 2006. Straw poll indicated: If editor is funded, SV-BC would like to receive first draft at least 1-year prior to freeze on changes. 2a) Because most of the work will fall on SV-BC, can you please answer the additional question of whether or not the committee is willing to self-fund the work if the P1800 cannot come up with the budget to fund the editor? Straw poll indicated very little support for this option. 3) Any other questions or comments to the study group as they consider their decision to develop the next PAR. Two items were discussed: Means to clearly communicate changes to public The deadline for the next revision The SV-BC approved the following responses: Cliff proposes to respond: The SV-BC committee supports the merge of P1800 & 1364 standards if a first draft is completed by an editor and the commitee has at least 1 year before the cut-off date for changes to the next revision of the standard to review it. Stu seconds. Opposed: Karen - Poor use of Karen's time and does not benefit her users Brad - Poor use of Brad's time and does not benefit his users Abstain: Shalom - Not a good use of committee's time Cliff proposes to respond The SV-BC requests that the next revision of the LRM be completed, balloted and approved by the end of 2008. Stu seconds. No Opposed. Abstain: Mark - Prefers scope of work determine deadline, not deadline determine scope of work. Logie - would prefer to define goal before setting deadline Cliff proposes to respond: SV-BC requests an editor throughout the process, would like a updated draft LRM with changes applied every 6 months and a mechanism for regularly communicating proposed changes to the public every 6 months. Gord seconds. No Opposed. No Abstain. Motion passes. AI: Matt to post minutes, notify reflector and have all review. If there are significant issues, there will be updated proposals put to an e-mail vote on Feb 13th. + Next Meeting Date: February 27th 10:58 AM: Cliff moves to adjourn Action Items Completed 01/09/2006 Matt update SVDB 1278 that it should wait until merge of 1364 & 1800 01/09/2006 Matt notify SV-EC/Mehdi that SVDB 1178 should be resolved by SV-EC 01/09/2006 Doug Update 631 in SVDB before vote. http://www.eda.org/svdb/bug_view_page.php?bug_id=0001297 01/09/2006 Doug transfer 624 to one of the associated SVDB issues (1004, 1072) and reference each issue to the other. http://www.eda.org/svdb/bug_view_page.php?bug_id=0001298 01/09/2006 Doug update proposal for 1253 to include a statement about polarity_operator not affecting simulation behavior 01/09/2006 Doug to update proposal for 664 per friendly amendment 01/09/2006 Dave Add bug note to SVDB 704 that this was ETF 613 01/09/2006 Gord remove Bugnote for SVDB 1188 01/09/2006 Steven add wording to SVDB 1246 that identifies why this is not an issue noting that the BNF allows only expressions as macro argmuments. 11/07/2005 Matt Send email Vote for: http://www.eda.org/svdb/bug_view_page.php?bug_id=871 http://www.eda.org/svdb/bug_view_page.php?bug_id=881 http://www.eda.org/svdb/bug_view_page.php?bug_id=882 http://www.eda.org/svdb/bug_view_page.php?bug_id=908 http://www.eda.org/svdb/bug_view_page.php?bug_id=911 http://www.eda.org/svdb/bug_view_page.php?bug_id=912 http://www.eda.org/svdb/bug_view_page.php?bug_id=919 http://www.eda.org/svdb/bug_view_page.php?bug_id=932 http://www.eda.org/svdb/bug_view_page.php?bug_id=941 http://www.eda.org/svdb/bug_view_page.php?bug_id=942 http://www.eda.org/svdb/bug_view_page.php?bug_id=944 http://www.eda.org/svdb/bug_view_page.php?bug_id=945 http://www.eda.org/svdb/bug_view_page.php?bug_id=946 http://www.eda.org/svdb/bug_view_page.php?bug_id=949 http://www.eda.org/svdb/bug_view_page.php?bug_id=952 http://www.eda.org/svdb/bug_view_page.php?bug_id=984 http://www.eda.org/svdb/bug_view_page.php?bug_id=1092 http://www.eda.org/svdb/bug_view_page.php?bug_id=1138 http://www.eda.org/svdb/bug_view_page.php?bug_id=1159 Pending 12/05/2005 Steven Ask Jay if issue 1127 is resolved in P1800? 01/09/2006 Shalom add example for issue 1254 describing situation for rule 3 01/09/2006 Matt assemble issue list for future work 01/09/2006 Matt find owners for future work issues 02/06/2006 Matt Close on committee agreed feedback for next PAR by Feb 17