HI Doron, Please, see my comments below. I am attaching a new version (also uploaded into Mantis). Thanks, Dmitry ________________________________ From: Bustan, Doron Sent: Wednesday, November 28, 2007 4:51 PM To: sv-ac@eda.org; Korchemny, Dmitry Subject: 1683 I have reviewed 1683. Here are my remarks: * End of page 2, "The zero delay indicated by ##0 is understood to be from the end point of the first sequence, which occurs at a tick of the first clock, to the nearest, non-strictly subsequent tick of the second clock, where the second sequence begins." I would replace "non-strictly" by "possibly overlapping". [Korchemny, Dmitry] I rewrote it as: "... occurs at a tick of the first clock, to the nearest, possibly overlapping tick of the second clock..." (deleted "subsequent" as well). Made this change in all similar cases. * At the end og page 3, I would add: If clk1 and clk2 are not identical, then the sequence @(posedge clk0) sig0 ##1 @(posedge clk1) sig1[*0:1] is illegal because of the possibility of an empty match of sig1[*0:1], which would make ambiguous whether the ending clocking event is @(posedge clk0) or @(posedge clk1). Like in a singly clocked sequence, the operands of ##0 shall not admit empty matches. [Korchemny, Dmitry] In singly clocked sequences the operands of ##0 may admit empty matches, e.g., a[*0:2] ##0 b[*0:2] is legal and it is equivalent to a[*1:2] ##0 b[*1:2]. As for the multiclocked sequences there is already a sentence in the original text: "When concatenating differently clocked sequences, the maximal singly clocked subsequences are required to admit only nonempty matches." * Need to modify 16.15.1 (a lot of work) [Korchemny, Dmitry] Done. Doron --------------------------------------------------------------------- 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.
This archive was generated by hypermail 2.1.8 : Mon Dec 03 2007 - 08:21:39 PST