Neil, The following lists the sections of merged LRM that we had prioritized for sv-ec members. This should be a start point for the sv-ec to review the cross-references, the mantis items and 'Questions'. Regards, - Mehdi --------- Merged LRM , 1800-draft2/3 Clause--------- section 3: Normative Design and Verification EC section 4: Scheduling semantics [Cliff, Heath] Section 7: Aggregate data types: EC. Mark/Dave Section 8: Classes EC. (Gord/Arturo/Francoise) Section 9: Processes EC (Gord/Cliff) Section 11: Operators expression (11.8 streaming operator) Dave (EC) Section 14: clocking blocks (mantis 890 affected section) Doug Arturo Section 15: Interprocess synchronization EC (Gord, Neil, Arturo) Section 16: Assertion AC Section 17: random EC (Ray, Francoise) Section 18: Functional coverage EC (Ray, Neil) Section 23: Program Block (EC) Doug, Mehdi Section 24: Interfaces BC/EC (Francoise, Dave) Section 39: code coverage (EC) Annex G: std package Annex H: linked list (for now ok, mantis will follow). Annex N: Algorithm/probability distribution function. (Mark) -----Original Message----- From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Neil Korpusik Sent: Wednesday, May 09, 2007 6:11 PM To: sv-ac@eda.org; 'Sv-Bc'; SV_EC List; SV-CC Cc: ieee1800@eda.org Subject: [sv-ec] Action required on the merged LRM - draft3 Hi all, At the last P1800 working group meeting it was agreed that we should proceed with the merged LRM. There will not be any more updates made to the 1364 LRM. Draft 3 of the P1800 LRM is now available. This is the first draft that has all of the SystemVerilog/Verilog merges in place. Below is a summary of the actions each committee will need to take. 1) Cross references Virtually every cross reference had to be replaced during the merge process. Since clause and subclauses were significantly restructured, Stu sometimes had to make subjective decisions on where the new cross references point to. Stu tried to be careful and thorough, but there was ample room for mistakes. Each committee should spend some time checking each cross reference in the clauses under their charge. 2) BNF excerpts All BNF excerpts should be reviewed to a) make sure the appropriate productions are in the excerpt. b) make sure the excerpts are up-to-date with the BNF. In particular, BNF excerpts from 1364 were replaced with excerpts from 1800. In some cases, the 1364 and 1800 BNFs were structured very differently. 3) Mantis proposals not yet reviewed by the Champions All resolved Mantis items that are pending Champions approval and implementation should be reviewed against Draft3 of the LRM. The subclause numbering for where changes need to be made may have changed and need updating. In some cases, the text to be corrected may have been removed (due to redundancy) or had other text merged in. 4) Margin notes from the editor Some of the margin notes begin with "QUESTION". These are red flags marking where Stu felt the merge had some ambiguity that was more than just editorial. Please start working on these tasks. Now that a decision has been made on the merged LRM, the Champions will start meeting on a regular basis. This will allow the editor to make updates over a period of time and not have a huge crunch at the end. I would like each chair to send me a list of the sections of the LRM that they plan to work on. That way I can make sure that every section will be covered. Neil -- --------------------------------------------------------------------- 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. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu May 10 10:08:45 2007
This archive was generated by hypermail 2.1.8 : Thu May 10 2007 - 10:08:57 PDT