Re: [sv-ac] 1900 Checkers

Hello Everyone,

Here are my comments so fare on the Mantis 1900 proposal "Checkers"
I'm still not done.  I still have to get through the section on free variables.

Tom


1.  Right before Syntax 9-1:  "four statements"  should be "five", because the
final block was added.

2.  Free Variables:  How are they randomized, How are they repeatable?

3.  A previous version of the proposal included covergroups as a possible
checker item.  Now they seem to have been taken out.  I'd like to see them in.

4.  p. 6.  "Checker action blocks shall not write into free variables, and
they may contain any code . . ."
	Re-write as "Action blocks within a checker shall not write into free
variables, but they may contain any other code . . ."

5.  p. 8.  "Since my_check1 instantiation is not in a scope of any conditional
statement, its inferred enable condition 1'b1."

Re-write as:  "If the enable pin connection had not been specified, the
inferred enable for the assertions in the my_check1 instantiation of the
checker would be be 1'b1, since it is not in the scope of any conditional
statement"

As is, the statement almost implied that the inferred enable would override
the value passed to the checker.

6.  Default clocking:  Are rules consistent?  For example, does default
clocking apply in module where it appears, any nested checker definitions, etc.

7.  What is the purpose for initial_check?  It's only to limit what may appear
in an initial block?
What kind of event controls are allowed.
Right off the bat, it doesn't seem like a very useful construct, since you
can't initialize anything in it.

8.  p. 12, example a:  Shouldn't the variable idx be 6 bits, not 64 bits?
	const freevar bit [5:0] idx;

That is enough bits to index a 64-bit variable.

9.  Note that example a would not work in simulation.  In simulation, idx
would be initialized to one value, which it would keep throughout the
simulation.  The corresponding bit of data1 and data2 would match, but the
other bits would not.

10.  Free variables can change at every time step?

11. Page 14:  Fragment sentence "This assignment shall at every time step."


Korchemny, Dmitry wrote On 09/19/07 02:27 AM,:
> Hi Lisa, Tom,
> 
>  
> 
> I uploaded the updated version of the proposal ready for review. This
> proposal does not contain a description of formal semantics yet.
> 
>  
> 
> Thanks,
> 
> Dmitry
> 
> ---------------------------------------------------------------------
> Intel Israel (74) Limited
> 
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
> 
> 
> -- 
> 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
408-616-5589
------------------

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