SV-BC Ballot Comment Resolution Meeting Date: Monday, April 27, 2009 Time: 9:00am-11:00am PDT Toll Free Dial In Number in North America: 1-888-813-5316 Caller Paid Dial In Number: 1-650-584-6338 Meeting ID: 7839818 21 Day 73 00 Month 44 00 Year 99 aa Matt Maidment - Intel aa Brad Pierce - Synopsys aa Mark Hartoog - Synopsys aa Dave Rich - Mentor Graphics aa Gordon Vreugdenhil - Mentor Graphics aa Stu Sutherland - Sutherland HDL aa Alex Gran - Mentor Graphics aa Heath Chambers - Consultant/Trainer aa Tom Alsop - Intel aa Francoise Martinolle - Cadence aa Cliff Cummings - Sunburst Design aa Shalom Bresticker - Intel aa Don Mills - LCDM Engineering aa Steven Sharp - Cadence Agenda + Review IEEE patent policy http://standards.ieee.org/board/pat/pat-slideset.ppt Reviewed. + Approve Previous Meeting Minutes http://www.eda.org/sv-bc/minutes/sv-bc_09_04_13.txt Cliff moves to accept. Tom seconds. No opposed. Abstain: Shalom (did not review them) Motion passes. + SV-CC Requesting SV-BC Input Per this e-mail: http://www.eda-stds.org/sv-bc/hm/9325.html the SV-CC is requesting input on the following items: http://www.eda.org/svdb/view.php?id=2642 http://www.eda.org/svdb/view.php?id=2643 Issues are generally asking why semantics of disable of DPI and Verilog functions are different. Issues are contradictory and propose 2 solutions to the same issue. Gord moves that these are beyond the scope of the ballot. Steve seconds. No opposed. No abstain. Motion passes. AI: Matt to update 2642 & 2643 with outcome of April 27 vote. + Ballot Comments 2692 Shalom believes this should be moved to SV-EC Brad moves to shift to SV-EC Steve seconds. No opposed. No abstain. Motion passes. AI: Matt notify Mehdi about 2692 2680 Shalom polled users. All he polled were strongly in favor of notification of invalid array write. Gord moves this is beyond the scope of the current schedule. Brad seconds. Opposed: Cliff, Don, Shalom, Heath, Tom, Stu Cliff: Would like to catch this error that's too often missed Don: Same as Cliff Shalom: Ditto Cliff and users want it before the next PAR Heath: Same as others. Tom: Same as others. Stu: Same reasons. For: Gord, Brad, Dave, Alex, Steve, Francoise, Mark Motion Passes. AI: Matt update 2680 with standard wording. 2611 Gord started a thread here: http://www.eda-stds.org/sv-bc/hm/9366.html AI: Gord to add clarification proposal for 2611 2720 Bind issue from SV-EC This likely needs some clarification. Should likely be tied in with resolution of 2663. 2721 Bind issue from SV-EC This needs clarification at the end of 23.11. AI: Steve will draft a proposal for 2721 2593 Clarification requested for 2 examples; Staying specific will help resolution. Otherwise, this could lead to significant work. This is important to resolve for ensuring implementations are consistent but it will take a lot of work. The amount of work required to bring implementations into alignment is significant. Scale of work more appropriate for next PAR. Gord moves that this beyond the scope of a ballot issue and should be considered in the future. Cliff seconds. Opposed: Francoise - Intent was clear in 1364 and it should be clarified now instead of waiting. Cliff - like to see a proposal Brad - Ought to be fixable. Steve - Like to see a proposal Tom - same reasons as Francoise Heath - same reasons as Francoise Stu - same reasons as Francoise For: Gord, Mark, Alex Abstain: Dave, Don Motion fails. AI: Steve to draft proposal for 2593 Shalom reminded group that by the next meeting we need to identify any issues that need more time and notify the 1800 WG. AI: Matt add agenda item to collect issues that need more time 2380 Contentious. Needs pre-discussion or pre-vote or review. Will take time, but valuable. AI: Cliff will raise 2380 in SV-EC. ----------------------------- 2681 May be a duplicate? Gord not sure it is illegal to use real as index of an array. Example or bullet below it needs to change. Some discussion required prior to any proposal. 2691 Should not take too long to resolve 1000 Point issue is trivial but addressing the entire proposal will need more time. 2697 There were reasons why this was not allowed in the LRM. Likely to be denied at this phase. 2669 Out of scope. 2678 Trivial. Likely just a comment with no action. 2673 Out of scope. 2679 Clarifying response with no action or out of scope. 2684 Beyond the scope of current LRM and potentially any future LRM. 2686 No change should be made. Not backward compatible. Out of scope. 2687 No proposal. Out of scope for current LRM. 2688 Out of scope. No proposal. 2689 Out of scope. No proposal. 2671 Out of scope or deny. 2580 Out of scope Next E-Mail Ballot 2568, 1791, 2674 AI: Matt propose to close the 'Out of Scope Issues' 11:00AM Meeting Adjourned Action Items Complete 04/13/2009 Brad create proposals for Mantis 2634, 2542, 2695, 1492 04/13/2009 Dave create proposals for Mantis 2550 04/13/2009 Shalom create proposals for Mantis 2676, 2672, 2683 04/13/2009 Stu create proposals for Mantis 2670, 2675 04/13/2009 Dave create proposals for Mantis 2568, 1791 04/13/2009 Matt consult Shalom on intentions for 2680 and 2692 04/13/2009 Gord provide initial answers to 2663, 2664, 2665 04/13/2009 Gord create proposals for Mantis 2674 Outstanding 04/13/2009 Brad create proposal for Mantis 1651 04/13/2009 Gord provide initial answers to Mantis 2610 04/27/2009 Matt to update 2642 & 2643 with outcome of April 27 vote. 04/27/2009 Matt notify Mehdi about 2692 04/27/2009 Matt update 2680 with standard wording. 04/27/2009 Gord to add clarification proposal for 2611 04/27/2009 Steve will draft a proposal for 2721 04/27/2009 Steve to draft proposal for 2593 04/27/2009 Matt add agenda item to collect issues that need more time 04/27/2008 Cliff raise 2380 in SV-EC