Hi John, Thx for the review -- I updated and posted. Thx. -Bassam. -----Original Message----- From: John Havlicek [mailto:john.havlicek@freescale.com] Sent: Thursday, July 05, 2007 7:14 AM To: bassam.tabbara@synopsys.COM Cc: sv-ac@eda-stds.org Subject: minor comments on 1599 Hi Bassam: I looked back over 1599. The changes to Clause 16 that I was worried about before are now gone -- I think 1768 is trying to deal with that part of the text. I have only a few minor suggestions. See below. J.H. 1599 Notes 2007-07-05 --------------------- . Additions for Clause 39.5.3. Is the vpi_get(vpiAssertFailureCovered, assertion_handle) being eliminated? I don't see any strikeout. In Draft3a this coverage type appears between vpiAssertVacuousSuccessCovered and the "in progress" equation. If the intention is only to add the text in blue, I think it will be clearer if ellipses are used to indicate omitted, unchanged text. Alternatively, include the unchanged text in black or make two separate change items for Clause 39.5.3. . Additions for Clause 39.5.3. I recommend changing For any assertion, the number of attempts that have not yet reached any conclusion (success or failure) can be derived from the formula: to For any assertion, the number of attempts that have not yet reached any conclusion (success, failure, disabled, killed) can be derived from the formula: RATIONALE: The current wording suggests that "success" and "failure" are the only possible conclusions. Alternatively, one could change "(success or failure)" to something like "(success, failure, etc.)". . Additions for Clause 39.5.3. For minor grammatical reasons, I recommend changing as there can be multiple matches corresponding to single attempt. to as there can be multiple matches corresponding to a single attempt. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Jul 5 08:44:44 2007
This archive was generated by hypermail 2.1.8 : Thu Jul 05 2007 - 08:45:00 PDT