RE: [sv-ac] Call to vote: Due August 22

Sending vote for 3033 only. Will send rest in a separate email:

Mantis 3033 ____ Yes _X___ No

http://www.eda-stds.org/mantis/view.php?id=3033

http://www.eda-stds.org/mantis/file_download.php?file_id=5325&type=bug

Here are my comments:

1. “If an actual argument contains any subexpression that is a const cast or automatic value from procedural code, then the corresponding formal argument shall be used only in static assertion statements (see 16.15.6) or static checker instances not be used in a continuous assignment or in the procedural code within the checker.” Why is this part changing ? What all is being included to use const cast/automatic variables now ? Also the following sentence “whenever a static assertion statement in the checker or a statically instantiated subchecker is added to the pending procedural assertion queue (see 16.15.6.1 and 17.3.1).” , now that checkers can only be instantiated statically inside another checker, is it required to state it ? Also, this checker which is instantiated in another checker, may not be a subchecker. In fact I did not find any other place where subchecker term is used.

2. In 17.3.1, the rules for concurrent assertions should be extended for deferred assertions also.

3. In 17.5, the paragraph “An always procedure in a checker body may contain deferred and concurrent assertions, nonblocking variable assignments (see 17.7.1) and a procedural timing control statement using an event control. All other statements shall not appear inside an always procedure.” Should be striken. Currently it is in blue.

4. In 17.5, the example shows that clk and rst are not sampled, but there is no text to support this exception.

5. “The always procedure in checkers allowed by IEEE Std 1800-2009, but always_comb, always_latch, and always_ff were forbidden. “ has ‘was’ missing.

6. Message: DELETE subclause 17.3.2 Nested checker instantiations” should be color coded as it is not visible.

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