RE: [sv-ac] idea of multi matches for cover

In the 2008 release of the standard, it is proposed that there exist a
"cover property" and a "cover sequence", where "cover property" will
report at most one match per attempt and "cover sequence" will report
multiple matches.  If you don't want the multiple matches per attempt,
just stick to using "cover property".  "cover property" will accept a
sequence argument also. Refer to Mantis 1768.  The previous version of
the standard was incomplete in that it did not specify how to determine
whether to treat the "cover property" expression as a sequence versus a
property.

Lisa

-----Original Message-----
From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of
Thomas Thatcher
Sent: Thursday, November 29, 2007 6:51 PM
To: danielm
Cc: sv-ac@eda-stds.org
Subject: Re: [sv-ac] idea of multi matches for cover

Hi Daniel,

What about using a *first_match* construct in the code to prevent
multiple
matches of a sequence?

    for example:

	cover property( first_match(a ##[1,$] b));

    or
	assert property( first_match(a ##[1,$] b));

This will eliminate the multiple matches you were talking about.

Tom

danielm wrote On 11/20/07 04:13 AM,:
> LRM wants that cover in contrast to assert and assume should react on
> all matches of sequence. This aproach may have big impact on
simulation
> performance - in some case properties used in cover wil have to be
> tracked from start point till end of simulation. Maybe there should be
> way to turn off such extra passes - similarly to switching off vacuous
> passes (see mantis  0001361)
> Such possibility to turn on off extra passes should be added to covers
> but also to assert and assume.
>  
> 
> LRM about cover directive> In addition, statement_or_null gets
executed
> for every match. If there are multiple matches at the same time, the
> statement gets executed multiple times, one for each match.
> 
>  
> 
> DANiel
> 
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and
is
> believed to be clean.

-- 
------------------
Thomas J. Thatcher
Sun Microsystems
------------------

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