The reference text changes in 1987. As currently defined, section 38.3.2 needs update. You need to assign this an assertion handle so you can do static checks, but I don't think callbacks make any sense. That also needs to be incorporated. My guess is that you will need to coordinate this with 1503. 38.3.2 Obtaining static assertion information The following information about an assertion is considered to be static: - Assertion name - Instance in which the assertion occurs - Module definition containing the assertion - Assertion type - Sequence Instance - Assert - Assume - Cover - Property Instance - ImmediateAssert - Assertion source information: the file, line, and column where the assertion is defined - Assertion clocking block/expression I'm actually questioning whether it makes sense to group this in the category of "expect" since it is not a check or coverage. It does not have an action block like assertion statements, it does not have callbacks, and it doesn't have any statistics counters. If this is the case, then model the VPI after expect (no change to 38.3.2, no changes relative to 1987 are needed. Perhaps have a section at the end that is called "Other Assertion Related Constructs" with a subsection for expect and restrict property. These differ from assertion statements in that they are not necessarily checks or coverage, but do operate off the underlying assertion properties. (wording needs help but hopefully you get the idea I am suggesting). If you do this, then you are also addressing 1522: clarifications on expect. You may also need to add this to the glossary. Are changes needed in the formal section? Lisa ________________________________ From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of Eduard Cerny Sent: Tuesday, February 05, 2008 5:22 PM To: sv-ac@eda.org Subject: [sv-ac] Updated proposal for Mantis - restrict property statement Hi, please find attached and also on Mantis, an updated proposal for the restrict property assertion statement, aligned with Draft 4. I did not have the source for the vpi diagrams hence I just pointed to the required change there. If someone has an editable form I would update the figure too. Let me know if you find any other issues. Best regards, ed -- This message has been scanned for viruses and dangerous content by MailScanner <http://www.mailscanner.info/> , 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 Wed Feb 6 05:50:00 2008
This archive was generated by hypermail 2.1.8 : Wed Feb 06 2008 - 05:50:19 PST