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.Received on Thu Nov 29 16:07:20 2007
This archive was generated by hypermail 2.1.8 : Thu Nov 29 2007 - 16:07:49 PST