RE: [sv-ac] [sv-ac] Review of IEEE P1800(tm)/D1, Mantis 2551

Yes.

The contents of the proposal for Mantis 2551 did not catch the sentence that precedes the code fragment.

In the code fragment itself, the font of "r1_" in"r1_p1" also needs to be corrected.

Shalom

From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of ben cohen
Sent: Sunday, May 08, 2011 4:06 AM
To: sv-ac@eda-stds.org
Subject: [sv-ac] [sv-ac] Review of IEEE P1800(tm)/D1, Mantis 2551

Page 437: The labeling of the assertions r1_p1 and r1_p2 do not match the text that refers to those assertions. Suggestion, fix the match in the text, as shown below:

For example, in the following code fragment, the clocking event @(posedge mclk) is inferred as the clocking event of r1_p1, while r1_p2 is clocked by @(posedge scanclk) as written:
property r1;
q != d;
endproperty
always @(posedge mclk) begin
q <= d1;
r1_p1: assert property (r1);
r1_p2: assert property (@(posedge scanclk)r1);
end

The resulting behavior of the above assertion r1_p2 depends on the relative frequencies of mclk and scanclk.

--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.
---------------------------------------------------------------------
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.