I agree that it was hard to figure out. Can we think of it as though the clock can only change after a "##1" or "|=>". This would imply that it cannot change after an "and" or "or" or other sequence operator. In 16.13.1, it states: "Multiclocked sequences are built by concatenating singly clocked subsequences using the single-delay concatenation operator ##1." And later it states: "Differently clocked or multiclocked sequence operands cannot be combined with any sequence operators other than ##1." Perhaps we can add something in the precedence table of 16-24? In this section we have not introduced multi-clk yet but ... Lisa -----Original Message----- From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of John Havlicek Sent: Friday, May 11, 2007 10:06 AM To: Eduard.Cerny@synopsys.com Cc: sv-ac@eda-stds.org Subject: Re: [sv-ac] Question on clock flow Hi Ed: My interpretation is (B). You will get (A) from @c (@d x) and y J.H. > X-Authentication-Warning: server.eda-stds.org: majordom set sender to > owner-sv-ac@eda.org using -f > X-MIMEOLE: Produced By Microsoft Exchange V6.5 > Content-class: urn:content-classes:message > Date: Fri, 11 May 2007 06:12:21 -0700 > Thread-Topic: Question on clock flow > Thread-Index: AceTzgJzYdlocUdEQrGSmaQxFC1Xrg== > From: "Eduard Cerny" <Eduard.Cerny@synopsys.com> > X-OriginalArrivalTime: 11 May 2007 13:12:23.0587 (UTC) > FILETIME=[03932730:01C793CE] > X-eda.org-MailScanner: Found to be clean, Found to be clean > X-Spam-Status: No, No > X-MIME-Autoconverted: from quoted-printable to 8bit by > server.eda-stds.org id l4BDCXkd025522 > Sender: owner-sv-ac@eda.org > X-eda.org-MailScanner-Information: Please contact the ISP for more > information > X-eda.org-MailScanner-From: owner-sv-ac@server.eda.org > > Hi, > > What is your interpretation of the clock flow in the LRM on the > following example: > > Question here to answer is what does @c (@d x and y) mean? A or B ? > ------------------------------------ > (A) (@d x) and (@c y) > (B) (@d x) and (@d y) > > ------- > > Thanks, > > ed > > -- > 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. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Fri May 11 11:24:38 2007
This archive was generated by hypermail 2.1.8 : Fri May 11 2007 - 11:25:06 PDT