Hi Dmitry,
The changes themselves look fine to me.
I have two concerns about the nexttime etc. operators (2552), though.
The parameter in brackets is designated as constant_expression. Tracking it on Annex A (via constant_expression, constant_primary, primary_literal, number) I can see it can in particular be a negative number or a real number. These do not make sense. The parameter should be a non-negative integer (or an expression evaluated as such).
The same comment goes to cycle_delay_const_range_expression used in always which is defined using constant_expression.
Another comment is about the verbal explanations of the operators. They are correct when there is a single clock, but incorrect in the presence of multiple clocks. In the presence of multiple clocks, a formula can be evaluated at a cycle which is not a tick of the clock of the nexttime operator. In such a case, the semantics dictates, that nexttime will take you to the second tick of the clock of the nexttime operator. (It is nexttime[0] that will take you to the first tick).
Regards,
Dana
From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of Korchemny, Dmitry
Sent: Tuesday, June 29, 2010 12:47 PM
To: sv-ac@eda.org
Subject: [sv-ac] Mantis items 2551 and 2552
Hi all,
I uploaded proposals for the following Mantis items
2551: trivial example error
http://www.eda-stds.org/mantis/file_download.php?file_id=4338&type=bug
2552: Confusing comments regarding nexttime operator
http://www.eda-stds.org/mantis/file_download.php?file_id=4345&type=bug
Please, review.
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. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Jun 30 20:57:12 2010
This archive was generated by hypermail 2.1.8 : Wed Jun 30 2010 - 20:57:18 PDT