Section 27.1.2

LRM-31

Changes:

Assertion Temporal expression—A declarative expression (one or more clock cycles) describing the behavior of a system over time. // This is the "body" of the assertion.

Remove editor’s note:

Editor’s Note: Why the underlined comment, above? Should it be regular text, or deleted?

Section 27.2

LRM-32

Changes:

 

These extensions shall be appended to merged into the contents of the vpi_user.h file, described in IEEE Std 1364-2001, Annex G. The numbers in the range 700 - 799 are reserved for the assertion portion of the VPI.

Remove editor’s note:

Editor’s Note: Is “shall”, which means mandatory, too strong here? It seems to infer that users or software vendors must modify the IEEE standard vpi_user.h header file, thereby making the file non IEEE compliant.

Section 27.2.3

LRM-33

Remove editor’s note:

Editor’s Note: This section is using some of the same constant values as the previous section.

Section 27.3.2

LRM-34

Changes:

— Assertion name

— Instance in which the assertion occurs

— Module definition containing the assertion

— Assertion directive

1) assert

2) check

3) assume

4) cover

5) sequence

6) Any assertion updates from the SV-AC.

— Assertion source information: the file, line, and column where the assertion is defined.

— Assertion clocking domain/expression2

— Assertion source information: the file, line, and column where the assertion is defined.

— Assertion clocking domain/expression

Remove editor’s notes:

Editor’s Note: Item 6, above, does not seem appropriate in a standard. Should it be deleted?

Editor’s Note: Are the two dashed-list lines above part of item 6?

Editor’s Note: What is the “2” in “expression2”, above?

Section 27.4.1

LRM-35

Changes:

27.4.1 Placing assertion system callbacks

Remove editor’s note:

Editor’s Note: Why is “system” in quotes?.

Section 27.4.2

LRM-36

Changes:

cbAssertionStepSucess

the progress along one path through the of one “thread” along an attempt. By default, step callbacks are not enabled on any assertions; they are enabled on a per-assertion/per-attempt basis, rather than on a per-assertion basis.

Remove editor’s note:

Editor’s Note: Why is “thread” in quotes?.

Section 27.5.2

LRM-37

Changes:

— For the following operator, the second argument shall be a valid assertion handle, the third argument shall be an attempt start-time (as a pointer to a correctly initialized s_vpi_time structure) and the fourth argument shall be a step control constant.

Remove editor’s note:

Editor’s Note: Why is “step control” in quotes?.