RE: [sv-ac] call to vote on Mantis 1361

The action block is the explicit production that appears as part of the
assert statement. 

I suggest changing:

SystemVerilog provides eight system tasks to control execution of
assertion action block for concurrent assertions:

to

SystemVerilog provides system tasks to control the pass and fail actions
associated with concurrent assertions:

> -----Original Message-----
> From: Kulshrestha, Manisha
> Sent: Wednesday, March 28, 2007 12:27 PM
> To: Rich, Dave; 'Jonathan Bromley'; 'john.havlicek@freescale.com';
'sv-
> ac@server.eda-stds.org'
> Subject: RE: [sv-ac] call to vote on Mantis 1361
> 
> Hi Dave,
> 
> These functions do affect the implicit fail action.
> 
> Manisha
> 
> -----Original Message-----
> From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org]
On
> Behalf Of Rich, Dave
> Sent: Wednesday, March 28, 2007 9:45 AM
> To: Jonathan Bromley; john.havlicek@freescale.com; sv-ac@server.eda-
> stds.org
> Subject: RE: [sv-ac] call to vote on Mantis 1361
> 
> 
> Another minor clarification is whether $assertfailon/off effects just
the
> explicit fail action, or also the implicit fail action of calling
$error.
> 
> Also, it is clear in this proposal that these tasks only control the
> execution of the action blocks of concurrent assertions. Shouldn't the
> same be true for section 22.8?
> 
> 
> Dave
> 
> > -----Original Message-----
> > From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org]
> On
> > Behalf Of Jonathan Bromley
> > Sent: Wednesday, March 28, 2007 3:20 AM
> > To: john.havlicek@freescale.com; sv-ac@server.eda-stds.org
> > Subject: RE: [sv-ac] call to vote on Mantis 1361
> >
> > This is probably too late, but I only just caught up with my email
> > backlog after being away...
> >
> > I think there is an ambiguity, or at least a lack of clarity, in the
> > proposed new clause "22.9 Assertion action control system
> tasks".
> > Do the $assertpasson/$assertpassoff tasks enable/disable the action
on
> > nonvacuous pass, or both vacuous and nonvacuous passes?  If they
> > control all forms of pass action, how do they interact with
> > $assertvacuouson/off?  For example, if I do
> >
> >   initial begin
> >     $assertpassoff;
> >     $assertvacuousoff;
> >     $assertpasson;
> >   end
> >
> > what will happen - is the $assertvacuousoff sticky, so that the
later
> > $assertpasson enables only non-vacuous successes?  It might be
> > preferable to express the effect in terms of three flags for each
> > assertion, one flag to enable each action - fail, non-vacuous
success,
> > vacuous succes - and then describe the effect of the $assert...
tasks
> > on those flags.
> > --
> > Jonathan Bromley, Consultant
> >
> > DOULOS - Developing Design Know-how
> > VHDL * Verilog * SystemC * e * Perl * Tcl/Tk * Project Services
> >
> > Doulos Ltd. Church Hatch, 22 Market Place, Ringwood, Hampshire, BH24
> 1AW,
> > UK
> > Tel: +44 (0)1425 471223                   Email:
> > jonathan.bromley@doulos.com
> > Fax: +44 (0)1425 471573                           Web:
> > http://www.doulos.com
> >
> > This e-mail and any  attachments are  confidential and Doulos Ltd.
> > reserves
> > all rights of privilege in  respect thereof. It is intended for the
> use of
> > the addressee only. If you are not the intended recipient please
> delete it
> > from  your  system, any  use, disclosure, or copying  of this
> document is
> > unauthorised. The contents of this message may contain personal
views
> > which are not the views of Doulos Ltd., unless specifically stated.
> >
> > --
> > This message has been scanned for viruses and dangerous content by
> > MailScanner, and is believed to be clean.
> >
> 
> 
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.