See the attachments. Neil -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. The resolution of "no change required" was unanimously approved by the Champions in the email vote that ended on May 14th, 2009. 2.1 2646 SV-AC Assumption in deferred assertion example should be made explicit 2.2 2657 SV-AC Clarify notion of sequence 2.3 2648 SV-AC Need an example of cyclic dependencies between sequences 2.4 2649 SV-AC sequence_actual_arg is used to represent the default argument 2.5 2655 SV-AC Backward compatibility issue with the clocking specification 2.6 2644 SV-CC Ballot comment #153 Wrong function named in table 36.9 2.7 2630 SV-CC Ballot comment #168 Wrong format type named in Table 38-5 2.8 2653 SV-AC Sequence match not shown in timing diagram 2.9 2717 SV-AC Ballot comment #81 Clarification needed for the usage of 2.10 2625 SV-CC Ballot comment #161 There is a blue change bar at the bottom 2.11 2622 SV-CC Ballot comment #156 Arrow missing in VPI Generate diagram 2.12 2632 SV-CC Ballot comment #16 Unimplemented Preponed PLI region clutters 2.13 2633 SV-CC Ballot comment #17 Unimplemented Post-Observed PLI region 2.14 2473 SV-EC Ballot comment #184 bit-stream cast to destination class must The proposal was unanimously approved by the Champions in the email vote that ended on May 14th, 2009. 2.15 2660 SV-AC Add indices to expressions 2.16 2478 SV-AC Clock flow subclause is not consistent with multiclocked 2.17 2541 SV-AC syntax errors - missing parenthesis 2.18 2516 SV-AC Another contradiction of existing text with 2398 needs 2.19 1775 SV-CC cbAtEndOfSimTime not in header files 2.20 2576 SV-CC Failed to remove reference to Reader API when deprecating Data 2.21 2623 SV-CC Ballot comment #157 vpiArrayType is labelled bool, should be int 2.22 2626 SV-CC Ballot comment #162 In Table 38-3 in vpiScalarVal, vpi1 et al 2.23 2631 SV-CC Ballot comment #172 The usage of the the term PLI is confusing 2.24 2647 SV-AC Clarification about clock glitches in concurrent assertions 2.25 2656 SV-AC Clarify difference of $global_clock handling in simulation and 2.26 2658 SV-AC Default values for untyped formals 2.27 2513 SV-BC BNF needs fixes to allow checkers in packages 2.28 2542 SV-BC Config declaration BNF bug 2.29 2550 SV-BC static variable initialization example has error 2.30 2634 SV-BC Ballot comment #20 Wording of paragraph implies evaluation 2.31 2672 SV-BC Ballot Comment #Macro expansion example incorrect in 22.5.1 2.32 2683 SV-BC Ballot comment #66: Example mislabelled "delay control" instead 2.33 2695 SV-BC Ballot comment #169: BNF error in edge_sensitive_path_declaration 2.34 2652 SV-AC Future value functions need clarification 2.35 2650 SV-AC Ambiguity in a sequence repetition [*0] definition 2.36 2670 SV-BC Ballot Comment #130: Module header description is missing the 2.37 2676 SV-BC Ballot comment #28: port connection warning 2.38 1492 SV-BC Overriding default lifetime of subroutine formal arguments 2.39 2627 SV-CC Ballot comment #163 In Tables 38-3 and 38-5, for decimal 2.40 2705 SV-EC Ballot Comment #35: Add example of string literal assignment 2.41 2682 SV-EC Ballot comment #42: Change "is" to "shall be" 2.42 2430 SV-EC associative array .first example should not have wildcard index 2.43 2701 SV-EC Ballot feedback item #44: Clarify rules for assignment to a 2.44 2706 SV-EC Remove reference to coding convention for class names 2.45 2713 SV-EC Ballot comment #47, misleading text in Table 8-1 2.46 2358 SV-EC (ballot 67) Actual arguments for base class cannot be specified 2.47 2596 SV-EC Ballot comment #80 Anachronistic and misleading text in 14.16 2.48 2612 SV-AC `true should have a backtick in a sequence example 2.49 2661 SV-AC "Syntax 16-19" is in blue. The proposal passed unanimously in the Champions conference call held on May 14th, 2009. 2.50 2719 SV-EC Editorial changes; See the editorial notes in the bug note from Shalom. The resolution of "open" was unanimously approved by the Champions in the email vote that ended on May 14th, 2009. 2.51 2642 SV-BC Ballot comment #151 Need a similar rule for disabled 2.52 2643 SV-BC Ballot comment #152 Section implies that a SystemVerilog The resolution of "won't fix" was unanimously approved by the Champions in the email vote that ended on May 14th, 2009. 2.53 2629 SV-CC Ballot comment #167 Function "vpi_get64" should be The Champions unanimously agreed to send the proposal back to the committee with a proposed rewording of the proposal. This was done and unanimously approved by the sv-ac May 26, 2009. 2.54 2659 SV-AC Backward compatibility issue with sequence property The resolution of "no change required" was unanimously approved by the Champions in the conference call held on May 14th, 2009. 2.55 2496 SV-AC non_port_program_item should contain assertion_item P1800 DRs, Not all of the ballot comments have reached the resolved state. Some of the ballot comments were marked as "must be satisfied". We are trying to gather input on those which were marked this way but are not not yet resolved. We are requesting that you help us gather this input from your member company. Below is a summary of all of the ballot comments that were marked "must be satisfied". 85 of the ballot comments were marked this way. Those that we would like to get feedback on are those that fall into one of the following categories. There are about 20 that fall into one of these categories. -- not resolved -- no consensus yet -- resolved, no proposal -- typically means no change will be made -- resolved, conflict -- was a controversial item I was unable to determine the mantis numbers for ballot comment #165, #166, #22 and #128. So I couldn't provide any details on their status. line 8 id 22 -- Editor mantis ?? ??? line 11 id 128 -- Editor mantis ?? ??? line 26 id 94 -- sv-ac mantis 2655 resolved, no proposal line 27 id 95 -- sv-ac mantis 2659 resolved line 30 id 97 -- sv-ac mantis 2478 resolved line 31 id 99 -- sv-ac mantis 2541 resolved line 32 id 100 -- sv-ac mantis 2516 resolved line 33 id 139 -- sv-ac mantis 2496 resolved, no proposal line 40 id 28 -- sv-bc mantis 2676 resovled line 42 id 2 -- sv-bc mantis 2477 resolved line 45 id 23 -- sv-bc mantis 2550 resolved line 49 id 33 -- sv-ec mantis 2380 not resolved, no proposal line 50 id 34 -- sv-ec mantis 2380 not resolved, no proposal line 51 id 56 -- sv-ec mantis 2380 not resolved, no proposal line 53 id 41 -- sv-ec mantis 2681 resolved line 56 id 3 -- sv-bc mantis 2501 resolved line 64 id 76 -- sv-bc mantis 2691 resolved line 69 id 123 -- sv-bc mantis 2674 resolved line 70 id 5 -- sv-bc mantis 1651 resolved, no proposal, conflict line 73 id 125 -- sv-bc mantis 2739 resolved line 74 id 126 -- sv-bc mantis 2672 resolved line 75 id 127 -- sv-bc mantis 2671 resolved, no proposal line 76 id 129 -- sv-bc mantis 2610 resolved, no proposal line 78 id 4 -- sv-bc mantis 2593 resolved, conflict line 85 id 142 -- sv-bc mantis 2513 resolved line 86 id 143 -- sv-bc mantis 2542 resolved line 87 id 169 -- sv-bc mantis 2695 resolved line 91 id 144 -- sv-cc mantis 2635 resolved line 92 id 145 -- sv-cc mantis 2636 resolved line 93 id 146 -- sv-cc mantis 2637 resolved line 94 id 147 -- sv-cc mantis 2638 resolved line 95 id 148 -- sv-cc mantis 2639 resolved line 96 id 149 -- sv-cc mantis 2640 resolved line 97 id 150 -- sv-cc mantis 2641 resolved line 98 id 151 -- sv-bc mantis 2642 resolved, no proposal line 99 id 152 -- sv-bc mantis 2643 resolved, no proposal line 101 id 157 -- sv-cc mantis 2623 resolved line 102 id 158 -- sv-cc mantis 2427 resolved line 103 id 154 -- sv-cc mantis 2645 resolved line 104 id 155 -- sv-cc mantis 2621 resolved line 106 id 159 -- sv-cc mantis 2582 not resolved has proposal line 107 id 156 -- sv-cc mantis 2622 resolved, no proposal line 111 id 164 -- sv-cc mantis 2628 resolved line 112 id 165 -- sv-cc mantis ?? ??? line 113 id 166 -- sv-cc mantis ?? ??? line 116 id 171 -- sv-cc mantis 2588 resolved line 118 id 172 -- sv-cc mantis 2631 resolved line 119 id 173 -- sv-cc mantis 1775 resolved line 120 id 174 -- sv-cc mantis 1775 resolved line 121 id 175 -- sv-cc mantis 2572 resolved line 122 id 176 -- sv-cc mantis 2572 resolved line 123 id 177 -- sv-cc mantis 2576 resolved line 128 id 20 -- sv-bc mantis 2634 resolved sv-cc sv-ec line 130 id 21 -- sv-ec mantis 2715 not-resolved, no proposal line 132 id 30 -- sv-ec mantis 2729 resolved line 133 id 31 -- sv-ec mantis 2729 resolved line 135 id 36 -- sv-ec mantis 2700 resolved line 136 id 37 -- sv-ec mantis 2700 resolved line 137 id 38 -- sv-ec mantis 2700 resolved line 138 id 39 -- sv-ec mantis 2700 resolved line 139 id 40 -- sv-ec mantis 2700 resolved line 141 id 43 -- sv-ec mantis 2430 resolved line 142 id 44 -- sv-ec mantis 2701 resolved line 144 id 45 -- sv-ec mantis 2430 resolved line 149 id 49 -- sv-ec mantis 2597 resolved line 153 id 67 -- sv-ec mantis 2358 resolved line 159 id 58 -- sv-ec mantis 2719 resolved line 160 id 59 -- sv-ec mantis 2575 not resolved, has proposal(email vote) line 163 id 62 -- sv-ec mantis 2606 not resolved, no proposal line 165 id 63 -- sv-ec mantis 2607 not resolved, no proposal line 166 id 65 -- sv-ec mantis 2723 resolved line 170 id 101 -- sv-ec mantis 2562 resolved line 171 id 102 -- sv-ec mantis 2718 resolved line 176 id 106 -- sv-ec mantis 2710 resolved line 177 id 107 -- sv-ec mantis 2711 not resolved, has proposal, conflict line 178 id 108 -- sv-ec mantis 2719 resolved line 182 id 112 -- sv-ec mantis 2719 resolved line 183 id 113 -- sv-ec mantis 2746 not resolved, has proposal(email vote) line 185 id 115 -- sv-ec mantis 2738 not resolved, has proposal, need pdf line 186 id 116 -- sv-ec mantis 2712 resolved line 187 id 117 -- sv-ec mantis 2719 resolved line 188 id 118 -- sv-ec mantis 2719 resolved line 190 id 121 -- sv-ec mantis 2750 not resolved, has proposal(email vote) line 191 id 122 -- sv-ec mantis 2543 resolved line 192 id 120 -- sv-ec mantis 2543 resolved Neil
This archive was generated by hypermail 2.1.8 : Thu May 28 2009 - 07:59:09 PDT