928: In addition to the item below, I noticed a question from the editor on 928 which is still not "closed". I reviewed the Mantis follow-up changes and I think everything is done. 1704: done - all changes were correctly incorporated. 1735: done - all changes were correctly incorporated. 1768: done except for two things: 1768-1) answering the editor's question "This code looks like a mix of BNF and example. Should it be all one or the other?": For a given attempt of the cover sequence statement, the total number of times matched for the attempt is equal to the number of times increment_match_coverage() is executed in the corresponding attempt of assert property ( [clocking_event] [ disable iff ( expression_or_dist ) ] sequence_expr |-> ( 1'b1, increment_match_coverage() ) ); For each execution of increment_match_coverage(), the pass statement of the cover sequence statement is executed in the Reactive region of the same timestep. 1768-2) cover statements have a "statement_or_null" instead of an action block, yet they all reference the assertion control system tasks of 19.11 that state they apply to action blocks. It is clear to me that only the "pass action block" controls apply but do we need to be more explicit? Lisa -----Original Message----- From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of John Havlicek Sent: Thursday, October 04, 2007 8:33 AM To: sv-ac@eda-stds.org Subject: [sv-ac] Draft4 review Hi Folks: We need to review the implementations in Draft4 of the following Mantis items: 1361 [TS/MK] 1460 [DK] 1550 [EC] 1674 [EC] (consider reference to 1648) 1677 [DK] 1704 [LP] 1730 [EC] 1734 [JH] 1735 [LP] 1768 [LP] The owners of these items should review the implementation and send the results to the reflector. Please consider any questions or issues in the notes from the Editor. I would like for the reviews to be completed in one week (by 2007-10-11). If the owner cannot do the review in this time, please try to find an alternate reviewer who can check the implementation in Draft4. J.H. -- 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 Mon Oct 8 14:12:37 2007
This archive was generated by hypermail 2.1.8 : Mon Oct 08 2007 - 14:13:04 PDT