Hi Lisa: I read 1768 carefully and had the comments below. J.H. Notes on 1768 2007-07-04 ------------------------ . p. 2, change to 16.14.3. I don't think the phrases "sequence coverage" and "property coverage" are clearly defined. I would change the following There exist two categories of cover statements, cover sequence and cover property. Both {\strikeout To} monitor {\strikeout sequences and other} behavioral aspects of the design for coverage. {\strikeout the same syntax is used with the cover statement}. The tools can gather coverage information about the evaluation and report the results at the end of simulation or on demand via an assertion API (refer to Clause 38). The difference between the two categories is that for sequence coverage(i.e. cover sequence), all-match semantics is required, whereas for property coverage (i.e. cover property), there is at most one match per attempt. to something like There exist two categories of cover statements, cover sequence and cover property. The cover sequence statement specifies sequence coverage, while the cover property statement specifies property coverage. Both {\strikeout To} monitor {\strikeout sequences and other} behavioral aspects of the design for coverage. {\strikeout the same syntax is used with the cover statement}. The tools shall gather coverage information about the evaluation and report the results at the end of simulation or on demand via an assertion API (refer to Clause 38). The difference between the two categories is that for sequence coverage, all matches per attempt shall be reported, whereas for property coverage, at most one match per attempt shall be reported. Also, please check the phrase "The tools shall gather". I'm not sure whether "The tools can gather" has the right meaning according to Clause 1.3. . p. 2, change to 16.14.3. Change In addition, statement_or_null is executed every time a property is being evaluated to true. to In addition, statement_or_null is executed every time a property is {\strikeout being} evaluated to true. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Jul 4 08:22:06 2007
This archive was generated by hypermail 2.1.8 : Wed Jul 04 2007 - 08:22:13 PDT