Hi Chas, There are several SV-CC mantis items that need to be updated so that they are consistent with draft 3a of the LRM. These changes were flagged in the Champions meeting of July 26, 2007. The technical committees are responsible for making sure that all of their mantis items are consistent with draft 3a. The editor is unable to determine the new section numbers on his own. It also should not be up to the champions to flag those mantis items that are not up to date with the merged LRM section numbering. Please make sure that all of the SV-CC mantis items are consistent with draft 3a before moving them to the resolved state. I also noted that several of these proposals have already been incorporated into draft 3a of the LRM. The next meeting of the P1800 working group will be on August 30th. I suggest that you try to get all of these updates done before then, so that the P1800 is able to approve these. The P1800 is usually given 2 weeks to review the set of mantis items approved by the Champions. I will be notifying the P1800 which set of mantis items have incorrect section numbers. It will be up to the P1800 working group to decide if any mantis items can be approved with the wrong section numbers or not. Getting the section numbers corrected before August 30 will be the best way to increase the likelihood of getting them into the next draft of the LRM. 985 cbSizeChange for queues too? 27.14 is now 36.16 1603 Unused vpiMultiArray declaration in vpi_user.h The change should be to Annex L (not annex G) AI/Francoise - Should this be in the backward compatibility section? If this constant was used it would be a problem. Make this change request in a separate mantis item. 1614 P1800-2005: 27.52 no expr for disable fork objects 27.52 is now 36.67 Isn't this change already contained in draft 3a? 1631 P1800-2005 27.14 note k has an error 27.14 item k) is now 36.16 item 11) Isn't this change already contained in draft 3a? 1632 P1800-2005 sections 27.14 note k and 27.22 note f are incompatible 27.22 is now 36.26 Isn't this change already contained in draft 3a? 1664 IEEE 1800-2005 27.7 Note 'e': First sentence should be rewritten 27.7 item e) is now 36.9 item 5) Isn't this change already contained in draft 3a? 1669 P1800-2005 Sections 27.34 and 27.36 commas are inconsistent 27.34 item b) is now 36.45 item 2) The set of changes includes the following 1. spelling error 2. adding an extra comma The editor may easily miss the fact that there are two changes to be made here. Dave added a bug note, but the mantis proposal should be redone to make the additional comma more obvious. It also appears that the spelling correction has already been made. 1684 vpiParent clarification needed for complex var/net objects 27.14 item z) is now 36.16 item 29) 27.13 item ab) is now 36.15 item 28) Note: when new text is added to the LRM it should be in blue. Stu agreed to not require it for this mantis proposal. Keywords should also be bolded. 1699 1800-2005+ draft 3 sections 36.34 and 36.68 problem with vpiReturn 36.34 - should be 36.51 36.68 - this section number is ok Annex M - the editor needs to change ### to an available number. The editor will add a margin note for this. - Francoise - the other numbers should remain as is. - Please confirm that this is what the editor should do. 1700 vpiTimeConst and vpiNullConst have the same value This change is now in Annex M 1716 Clarify handling of DPI formals/actuals with rand/randc qualifier F.5 is now I.5 Neil Charlie Dawson wrote On 08/14/07 11:26,: > Our next SV-CC meeting is on 08/15/2007. > > The call-in information for this meeting is as follows: > > U.S. 866-807-0627 > International 203-955-5179 > Passcode 399143 > > Meeting will start at 11:30am EDT (3:30pm GMT), and last for 1.5 hours. > > AGENDA > > 1. Review Patent information > > Go to: > http://standards.ieee.org/board/pat/pat-slideset.ppt > > 2. Review minutes from last meeting (07/18/2007 and 08/01/2007) > > 3. Liaisons > > - Francoise to report on PASSED SV-BC items > - Anyone care to make a report? > > 4. New business > > - Item 1865 Definition of `s_vpi_vecval' in `svdpi.h' and `vpi_user.h' > - Item 1946 Clarify vpiSize for string vars and other SystemVerilog variable types > - Item 1947 vpiTask, vpiFunction for built-in method calls > - Item 1599 The assertion API and VPI sections need changes as per mantis #805 > - Item 1361 need a way to control execution of action blocks > - Item 1952 "Null argument" to mean "omitted argument" may be confusing > - Item 1603 Unused vpiMultiArray declaration in vpi_user.h > - Item 1942 Deprecated vpiArray property still appears in several places where vpiArrayMember should replace it. > - Item 1970 What is vpiIndexTypespec for an array with a wildcard index type? > - Item 1696 What is vpiRange for a dynamic array, assoc. array, queue? > - Others? > > 5. Review SV-CC items with proposals: > > 6. Review SV-CC items with proposals (Straw poll only): > > - Others? > > 7. Review old business: > > - Francoise and Bassam to continue work on assignment patterns. > - Francoise to champion adding support for typed parameters to the > typespec diagrams. > - Abi to champion adding support for parameterized classes. > - Abi/JimV to champion improving the ability to compare objects. > - Steve to send out exact text on referring to a prior version. > - Chas to take a look for questions from Editor in these sections > and either answer them himself or parcel them out to other > committee members as appropriate. > > > -- --------------------------------------------------------------------- Neil Korpusik Tel: 408-276-6385 Frontend Technologies (FTAP) Fax: 408-276-5092 Sun Microsystems email: neil.korpusik@sun.com --------------------------------------------------------------------- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Tue Aug 14 18:06:25 2007
This archive was generated by hypermail 2.1.8 : Tue Aug 14 2007 - 18:06:48 PDT