RE: [sv-ac] #1361.

Hi Dmitry, Agreed. 

The VPI assertion control is somewhat more elaborate (talks about
attempts), see 28.4.2, we also need to make sure this part is
consistent.

Thx.
-Bassam.

-----Original Message-----
From: Korchemny, Dmitry [mailto:dmitry.korchemny@intel.com] 
Sent: Monday, May 22, 2006 7:49 AM
To: Bassam Tabbara; sv-ac@eda.org
Subject: RE: [sv-ac] #1361. 

Hi Bassam,

Even the definition given in LRM is not clear:

SystemVerilog provides three system tasks to control assertions.
- $assertoff shall stop the checking of all specified assertions until a
subsequent $asserton. An assertion that is already executing, including
execution of the pass or fail statement, is not affected.
- $assertkill shall abort execution of any currently executing specified
assertions and then stop the checking of all specified assertions until
a subsequent $asserton.

What does "assertion that is already executing" mean? When there is an
active thread of the assertion? Or when the action block is executed?

We need first to make this definition clear.

Thanks,
Dmitry

-----Original Message-----
From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org] On
Behalf Of Bassam Tabbara
Sent: Wednesday, May 10, 2006 7:20 AM
To: sv-ac@server.eda.org
Subject: [sv-ac] #1361

I vote no:
 
- must add VPI controls to proposal.
- I think tasks should be consistent with asserton/off tasks, i.e. not
disable in-flight assertions