RE: [sv-ac] event triggered in concurent assertion

Hi Ed,

 

Is there a reason you cannot use e.triggered in a concurrent assertion
versus e.ended?  I thought you could use e.triggered anywhere you can us
e.ended?

 

Lisa

 

________________________________

From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of
Eduard Cerny
Sent: Monday, March 17, 2008 7:41 AM
To: danielm; sv-ac@eda-stds.org
Subject: RE: [sv-ac] event triggered in concurent assertion

 

Daniel, in this case e.ended is allowed. .triggered is to be used
outside assertion or in disable iff.

Regards,

ed

 

 

From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of
danielm
Sent: Monday, March 17, 2008 5:26 AM
To: sv-ac@eda-stds.org
Subject: [sv-ac] event triggered in concurent assertion

 

LRM specifies that using event in concurent assertion is forbidden - but
how about using triggered property? LRM do not precise that.

 

module top;

    bit precond;

    event e;

    assert property (@(posedge clk) precond |-> e.triggered);

endmodule

 

 

 

DANiel


-- 
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 <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.