Hi Dimitry,
I have fixed the disable iff thing. Please upload the files.
Thanks.
Manisha
From: Korchemny, Dmitry [mailto:dmitry.korchemny@intel.com]
Sent: Tuesday, November 29, 2011 6:32 PM
To: Kulshrestha, Manisha
Cc: sv-ac@eda-stds.org
Subject: RE: Mantis 3295: need a way to control only asserts/covers/assume directives
Hi Manisha,
Several minor comments:
· Why don’t the changes come in their order in the LRM?
· The Table 20-8 header should be typeset as its last column is. See Table 20-5 in the LRM as an example. (sorry for missing it earlier)
· Page 11, Clause 16.9.4, both cases: typeset “disable iff” as a keyword.
· Page 11, bottom. Typeset editor note “Clause 16.3, change:” properly
· Page 12. Typeset “assert” and “else” as keywords
· Page 12, Annex M.2,. Typeset #define statements as code.
· Also last two blue defines on Page 13.
· Page 14. “can not” à “cannot”
Thanks,
Dmitry
From: Kulshrestha, Manisha [mailto:Manisha_Kulshrestha@mentor.com]
Sent: Tuesday, November 29, 2011 14:40
To: Korchemny, Dmitry
Cc: sv-ac@eda-stds.org
Subject: RE: Mantis 3295: need a way to control only asserts/covers/assume directives
Hi,
I am attaching updated version of the proposal here based on Dimitry and Sholom’s latest comments. Now, table 20-8 has changed (merged tables 20-8 and 28-9) and also vpi related stuff is new related to lock/unlock. Please review it.
Thanks.
Manisha
From: Korchemny, Dmitry [mailto:dmitry.korchemny@intel.com]
Sent: Tuesday, November 29, 2011 1:05 PM
To: Kulshrestha, Manisha
Subject: Mantis 3295: need a way to control only asserts/covers/assume directives
Hi Manisha,
It looks to me that the tables describing VPI callbacks are missing entries with assertion lock/unlock. If it is so, also the corresponding defines should be added.
Minor comment:
In tables 20-8,9 assertion control system task names, such as $asserton, $assertcontrol, etc., should be typeset as code.
Thanks,
Dmitry
---------------------------------------------------------------------
Intel Israel (74) Limited
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
This archive was generated by hypermail 2.1.8 : Tue Nov 29 2011 - 09:49:13 PST