Toll Free Dial In Number: (866)839-8145 Int'l Access/Caller Paid Dial In Number: (215)446-3660 ACCESS CODE: 9301228 Hi Champions, We are scheduled to meet tomorrow morning, Thursday May 21st, 8AM PST. The sv-cc and sv-ac have responded to the Champions feedback from the May 14th conference call. The proposals for the following mantis items are now ready for the champions. 1. 2621 sv-cc The following concern was noted by the Champions. In the May 14th conference call the Champions unanimously agreed to send the proposal back to the committee for review to make sure that the following was noted by the committee and that they still believe that the proposal is consistent with the rest of the text in the LRM. The proposal says, "If the vpiSize of the vpiReturn variable is defined (see 37.17, detail 9) and can be determined without evaluating the function (see 37.3.5), vpiSize for the function shall return the same value as vpiSize for the vpiReturn variable... For all other cases the behavior of vpiSize is undefined." 37.3.5 talks specifically about evaluating functions with side effects, not about function evaluation without side effects. Is this consistent? 37.3.5 only talks about functions with side effects. The other text is unconditional. 2. 2637 sv-cc In the May 14th conference call the Champions noted that the proposal doesn't make any updates to the subclause that was mentioned in the ballot feedback. There were some changes made in the same general area, but not the specific changes mentioned by the ballot feedback. The ballot comment specifically referenced subclause 35.5.1.3, where there are 2 references to PLI. The proposal does not fix this subclause. 3. 2654 sv-ac -- the Framemaker files were created for the Editor The proposal failed to pass in the Champions email vote that ended on May 14th, 2009. The Champions noted that the Editor will require new diagrams from the committee. A Framemaker source file for this change to the diagram would be best. The current format for these diagrams cannot be Edited and need to be redone. Neil -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. Hi Champions, Below is the set of mantis items that are up for a vote by the Champions. We will be meeting this Thursday, May 21st, 8am PST. If you have time, it would be good if you could send out your votes before the meeting. That way I can combine the results before the meeting starts. That would make the meeting go quite a bit faster. I will attempt to send another version of this later today that has more details. 1. 2739 SV-BC Ballot comment 125: Conflict in strength number/name; 5 is not large Yes ___ No ___ Abstain ___ 2. 2738 SV-EC Ballot comment #115 Automatic bin creation for coverage points (up to N-1) Yes ___ No ___ Abstain ___ 3. 2737 SV-EC Ballot Comment #54: restricting access of local paramters inside a class Yes ___ No ___ Abstain ___ 4. 2735 SV-EC Ballot Comment #48: Chaining of method calls Yes ___ No ___ Abstain ___ 5. 2730 SV-EC Ballot comment 114: State bins has not been defined before Yes ___ No ___ Abstain ___ 6. 2729 SV-EC Ballot comments 30 and 31: Ambiguity regarding valid data types to packed structures/unions Yes ___ No ___ Abstain ___ 7. 2724 SV-EC Ballot Comment #51 Clarification of super.new statement in 8.14 Yes ___ No ___ Abstain ___ 8. 2723 SV-EC Ballot comment #65 class decls must be in the same scope as the forward Yes ___ No ___ Abstain ___ 9. 2718 SV-EC Ballot comment #102 dist_item occurs twice in Syntax 18-3 Yes ___ No ___ Abstain ___ 10. 2712 SV-EC Ballot comment #116 19.5.6 Value resolution needs to clarify rules in context of wildcard bins Yes ___ No ___ Abstain ___ 11. 2700 SV-EC Ballot feedback items 36-40: type rules for strings Yes ___ No ___ Abstain ___ 12. 2698 SV-EC Ballot comment #57: pure keyword SHALL be required Yes ___ No ___ Abstain ___ 13. 2691 SV-BC Ballot comment #76: suspension of function execution Yes ___ No ___ Abstain ___ 14. 2689 SV-BC Ballot comment #73: x in case expressions Yes ___ No ___ Abstain ___ 15. 2688 SV-BC Ballot comment #72: unique-if and x/z values Yes ___ No ___ Abstain ___ 16. 2687 SV-BC Ballot comment #70: expression bit-length enhancements Yes ___ No ___ Abstain ___ 17. 2686 SV-BC Ballot comment #69: Bit/Part-select errors should be reported uniformly. Yes ___ No ___ Abstain ___ 18. 2684 SV-BC Ballot comment #68: Non-constant width part-select enhancement Yes ___ No ___ Abstain ___ 19. 2681 SV-EC Ballot comment #41: Bad associative array example Yes ___ No ___ Abstain ___ 20. 2679 SV-BC Ballot comment #29: static casting Yes ___ No ___ Abstain ___ 21. 2674 SV-BC Ballot Comment #123: Incorrect syntax for $fopen in 21.3.1 Yes ___ No ___ Abstain ___ 22. 2673 SV-BC Ballot comment #26: Deprecate defparams Yes ___ No ___ Abstain ___ 23. 2671 SV-BC Ballot Comment #127 Deprecate or discourage use of `define Yes ___ No ___ Abstain ___ 24. 2645 SV-CC Ballot comment #154 Properties returning DPI information on task/function declaration are missing Yes ___ No ___ Abstain ___ 25. 2641 SV-CC Ballot comment #150 Formal argument types for import /export subroutines should include time and integer Yes ___ No ___ Abstain ___ 26. 2640 SV-CC Ballot comment #149 Using the string "DPI" should result in a compile time warning Yes ___ No ___ Abstain ___ 27. 2639 SV-CC Ballot comment #148 Simplify definition of import/export call chains. Yes ___ No ___ Abstain ___ 28. 2638 SV-CC Ballot comment #147 no explicit behavior of a call to a DPI export subroutine Yes ___ No ___ Abstain ___ 29. 2636 SV-CC Ballot comment #145 contradition for return value of imported tasks Yes ___ No ___ Abstain ___ 30. 2635 SV-CC Ballot comment #144 tasks consuming time contradiction in LRM Yes ___ No ___ Abstain ___ 31. 2624 SV-CC Ballot comment #160 Diagram has a blue arrow that should be black Yes ___ No ___ Abstain ___ 32. 2611 SV-BC Resolution of names containing :: Yes ___ No ___ Abstain ___ 33. 2610 SV-BC Name resolution in presence of type parameters needs to be clarified Yes ___ No ___ Abstain ___ 34. 2597 SV-EC Ballot comment #49 When do class property initializers execute in relation with the constructor call Yes ___ No ___ Abstain ___ 35. 2593 SV-BC Omitting types in port declaration Yes ___ No ___ Abstain ___ 36. 2588 SV-CC Omission of package as a legal context in which DPI imports can be declared Yes ___ No ___ Abstain ___ 37. 2580 SV-BC %p should allow radix specification Yes ___ No ___ Abstain ___ 38. 2568 SV-BC unpacked array terminology unclear in $readmem $writemem Yes ___ No ___ Abstain ___ 39. 2514 SV-EC Ballot comment #182 External constraint blocks not defined well Yes ___ No ___ Abstain ___ 40. 2510 SV-EC Ballot comment #183 Allowed types for clocking signal is too restrictive Yes ___ No ___ Abstain ___ 41. 2501 SV-BC implication operator (->) should short-circuit and equivalence operator (<->) should evaluate operands only once Yes ___ No ___ Abstain ___ 42. 2486 SV-AC Scope of Annex F definition of "specify" is not clear. Yes ___ No ___ Abstain ___ 43. 2477 SV-BC How are values of enumeration constants calculated? Yes ___ No ___ Abstain ___ 44. 2468 SV-CC vpiStartLine vpiColumn vpiEndLine vpiEndColumn assertion properties all undefined in include file Yes ___ No ___ Abstain ___ 45. 2427 SV-CC vpiEdge, vpiDirection should be int, not bool Yes ___ No ___ Abstain ___ 46. 2342 SV-EC Class constructor should not be allowed to be static or virtual (p1800-2009 ballot id 185) Yes ___ No ___ Abstain ___ 47. 2288 SV-EC Ballot comment #186 Re: Associative array next() & prev() Yes ___ No ___ Abstain ___ 48. 1791 SV-BC atoi(), atohex(), atooct(), atobin() should warn about truncation Yes ___ No ___ Abstain ___ 49. 1651 SV-BC $psprintf Yes ___ No ___ Abstain ___ 50. 1256 SV-EC Minor problems in description of Linked Lists (Annex H) [p1800-2009 ballot comment id 192] Yes ___ No ___ Abstain ___ NeilReceived on Wed May 20 17:54:51 2009
This archive was generated by hypermail 2.1.8 : Wed May 20 2009 - 17:54:55 PDT