RE: [sv-ac] Call to vote: Due June 20

Hi Manisha,

Please, see my comments below.

Thanks,
Dmitry

From: Kulshrestha, Manisha [mailto:Manisha_Kulshrestha@mentor.com]
Sent: Monday, June 20, 2011 13:23
To: Korchemny, Dmitry; sv-ac@eda-stds.org
Subject: RE: [sv-ac] Call to vote: Due June 20

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=5152&type=bug

I need more time to review this proposal. The last proposal on sampling had a reference about sampling of checker actual arguments. That should be fixed now.
[Korchemny, Dmitry] I found one such place that should be fixed: "Concurrent assertions and several other constructs (such as checker actual arguments, see 17.3)". Done.

Also, now since sampling is discussed in this proposal for different types of procedual blocks, it should be made clear that concurrent assertions use sampled values irrespective of where they are.
[Korchemny, Dmitry] Should we? It is stated in16.5 that all variables in concurrent assertions are sampled, and nowhere is stated that there are exceptions from this rule. Note, that it is not written that everything in always_comb procedures in checkers is not sampled, therefore it looks to me that there should be no need to explicitly confirm the sampling rule for concurrent assertions.

Also, if there is a deferred or simple immediate assertion in always block, does it use sampled value or current value ?
[Korchemny, Dmitry] I added a clarification and updated the example.

Mantis 3069 _ X ___ Yes ____ No

http://www.eda-stds.org/mantis/view.php?id=3069
http://www.eda-stds.org/mantis/file_download.php?file_id=5142&type=bug

Below are the changes made in 3069:

- Replaced "global clocking declaration in effect" with "effective global clocking declaration"

- Fixed punctuation and spelling

- Changed
However, any of its instances in the elaborated design description shall contain at most one global clocking declaration. It shall be an error if there is more than one global clocking declaration in a given module, interface, checker or program instance in the elaborated design description.
To
However, any of its instances in the elaborated design description shall contain at most one global clocking declaration; it shall be an error otherwise.

- Changed
When global clocking is referenced in a sequence declaration, a property declaration, or as an actual argument to a named sequence instance, a named property instance, or a checker instance, the point of reference shall be considered after the application of the rewriting algorithm defined in F.4.1, which flattens properties and sequences, and substitutes actual arguments to sequence, property and checker instances for their corresponding formal arguments. As a result, when a property or a sequence declaration containing a reference to global clocking is instantiated in an assertion statement, the hierarchical lookup rules described above shall be applied from the place of the assertion statement appearance in the source description, not from the point of the sequence or the property declaration. Similarly, when global clocking is referenced in an actual argument of a checker instance, the lookup rules shall be applied after the substitution of the actual argument in place of the corresponding formal argument inside the checker body.
To
When global clocking is referenced in a sequence declaration, a property declaration, or as an actual argument to a named sequence instance, a named property instance, or a checker instance, the point of reference shall be considered after the application of the rewriting algorithm defined in F.4.1. As a result, when a property or a sequence declaration is instantiated in an assertion statement, the hierarchical lookup rules described above shall be applied from the place of the assertion statement appearance in the source description, not from the point of the sequence or the property declaration. Similarly, the lookup rules shall be applied after the substitution of the actual argument in place of the corresponding formal argument inside the checker body.

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