RE: [sv-ac] comments on 1681

I uploaded the updated version based on Tom's and John's comments.

Thanks,
Dmitry

-----Original Message-----
From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org] On
Behalf Of John Havlicek
Sent: Tuesday, July 17, 2007 5:30 PM
To: sv-ac@server.eda-stds.org
Subject: [sv-ac] comments on 1681

All:

I have reviewed the proposal for 1681.  My comments are below.

J.H.

2007-07-17
----------

p. 3.  "One clocking can be specified ..." is unusual.  Throughout
Clause 14,
   "clocking" seems to be a participle (adjective) rather than a gerund
(noun).  
   Note that in 14.12, the corresponding text now reads 

      One clocking block can be specified ... 

   in Draft 3a.  I recommend changing either to this form or, if this
form is not 
   desired due to the limited form of a global clocking declaration,
then to
   
      One clocking declaration can be specified ...

p. 3.  I don't understand

      Only one global clocking can be specified anywhere in the design
      in any one compilation unit of the design

   How are the two phrases 

      anywhere in the design

   and   

      in any one compilation unit of the design

   supposed to be related?  The second seems more restrictive than the
first.
   We should make sure that these are equivalent to the parenthetical

      (i.e., global clocking must have at most one definition on the
      entire model after elaboration)

   Maybe it is better to find one clear way to say this and reduce from
three
   to one.

p. 3.  LRM-ese.  I think 

      Only one global clocking can be specified

   should be

      Only one global clocking may be specified

   Also, I think

      It is an error if there is more than one

   should be 

      It shall be an error if there is more than one

p. 4.  Change

      in simulation $global_clock is substituted by

   to

      in simulation $global_clock is replaced by

p. 4.  For clarity, I recommend changing

      the assertion states that a remains true at each tick of the
      global clock, which is interpreted in simulation as 

         assert property(@clk a);

   to

      the assertion states that a remains true at each tick of the
      global clock.  In simulation, this assertion is equivalent to 

         assert property(@clk a);

p. 4.  Change the reference to "E.3.1" to the appropriate reference in 
  Annex F.

p. 4.  The change to 21.13.2 is not appropriate.  That section describes

   1800-2005 keywords and how to limit the reserved words to that set.
   Presumably, 1800-2008 will have an analogous section where "global" 
   should be added.

p. 7.  The rightarrows (long mapsto) are missing in the clock rewrite
  rules.  It would be good to fix this to avoid confusion.


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