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

Hi Erik,

Please, see my comments below.

Thanks,
Dmitry

From: Seligman, Erik
Sent: Saturday, August 06, 2011 00:39
To: Korchemny, Dmitry; sv-ac@eda-stds.org
Subject: RE: Call to vote: Due August 8

My votes:

Mantis 2578 __X_ Yes ____ No
http://www.eda-stds.org/mantis/view.php?id=2578
http://www.eda-stds.org/mantis/file_download.php?file_id=5251&type=bug

Mantis 3033 _X__ Yes ____ No
http://www.eda-stds.org/mantis/view.php?id=3033
http://www.eda-stds.org/mantis/file_download.php?file_id=5257&type=bug

Friendly amendments:

- p.9, example: check_outside is missing an arg
[Korchemny, Dmitry] Fixed.

- p.15, 1st bullet point: "In always_ff procedure" ==> "In always_ff procedures"

[Korchemny, Dmitry] Fixed.

C.2.7: Rephrase 1st paragraph: "The always procedure allowed by IEEE Std 1800-2009 in checkers, but always_comb, always_latch, and always_ff were forbidden. The limitations imposed on the always procedure in checkers included the limitations imposed on always_ff procedures outside checkers. In this version of the standard always_comb, always_latch, and always_ff have been added for checkers. As a result the general always procedure in checkers would have imposed the same limitations as always_ff does. Therefore the usage of always procedures in checkers is deprecated and does not appear in this version of the standard."

[Korchemny, Dmitry] Done.

Also, a question about 17.3. Since we're adding a new limitation on checkers containing procedural code, is it important for us to include an example with a deferred assertion outside a procedure, and point out how its implicit always_comb prevents its checker from being instantiated by other checkers?
[Korchemny, Dmitry] My understanding is that deferred assertions are allowed and they become procedural, as concurrent assertions do. I need to add a clarification. Let's discuss it at today's meeting.

---------------------------------------------------------------------
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, and is
believed to be clean.