RE: [sv-ac] Samppled value functions

From: Eduard Cerny <Eduard.Cerny_at_.....>
Date: Tue May 29 2007 - 07:53:42 PDT
Hi John,

the change in the text is in 1737.
ed
 

> -----Original Message-----
> From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On 
> Behalf Of John Havlicek
> Sent: Tuesday, May 29, 2007 10:47 AM
> To: dmitry.korchemny@intel.com
> Cc: sv-ac@eda-stds.org
> Subject: Re: [sv-ac] Samppled value functions
> 
> Hi Dmitry:
> 
> Here is what I think the definition ought to be.
> 
> $rose, $fell, $stable compare the current timestep preponed 
> value of their first argument expression to another value.
> 
> This other value is supposed to be the preponed value of 
> the first argument expression at the nearest strictly prior
> timestep in which the clocking event occurred.  
> 
> However, if there is no such strictly prior timestep in which 
> the clocking event occurred, then I think the other value 
> should be the default initial value of the first argument expression,
> rather than just X.
> 
> I actually thought we had changed this already, but maybe it is
> in a proposal that has not yet been passed.
> 
> Do you agree?
> 
> Once we agree on a precise definition, Annex F needs to be 
> rewritten to conform to it.
> 
> J.H.
> 
> > X-Authentication-Warning: server.eda-stds.org: majordom set 
> sender to owner-sv-ac@eda.org using -f
> > X-ExtLoop1: 1
> > X-IronPort-AV: E=Sophos;i="4.14,588,1170662400"; 
> >    d="scan'208,217";a="250688893"
> > X-MimeOLE: Produced By Microsoft Exchange V6.5
> > Content-class: urn:content-classes:message
> > Date: Tue, 29 May 2007 14:42:24 +0300
> > X-MS-Has-Attach: 
> > X-MS-TNEF-Correlator: 
> > Thread-Topic: Samppled value functions
> > Thread-Index: Aceh5myXFfNOPpJuT5S1L9dQU/MQLQ==
> > From: "Korchemny, Dmitry" <dmitry.korchemny@intel.com>
> > X-OriginalArrivalTime: 29 May 2007 11:42:42.0542 (UTC) 
> FILETIME=[77A858E0:01C7A1E6]
> > X-eda.org-MailScanner: Found to be clean, Found to be clean
> > X-Spam-Status: No, No
> > 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
> > 
> > This is a multi-part message in MIME format.
> > 
> > ------_=_NextPart_001_01C7A1E6.6CE6D161
> > Content-Type: text/plain;
> > 	charset="us-ascii"
> > Content-Transfer-Encoding: quoted-printable
> > 
> > Hi all,
> > 
> > =20
> > 
> > There is some inconsistency between the LRM body and the formal
> > semantics. According to LRM (clause 16.8.3):
> > 
> > =20
> > 
> > A value change function detects the change in the sampled 
> value of an
> > expression. The clocking event is
> > 
> > used to obtain the sampled value of the argument expression 
> at a clock
> > tick prior to the current simulation
> > 
> > time unit. Here, the current simulation time unit refers to the
> > simulation time unit in which the function is
> > 
> > evaluated. This sampled value is compared against the value of the
> > expression determined at the Preponed
> > 
> > time of the current simulation time unit. The result of a 
> value change
> > expression is true or false and can be
> > 
> > used as a boolean expression.
> > 
> > - $rose returns true if the LSB of the expression changed to 1.
> > Otherwise, it returns false.
> > 
> > - $fell returns true if the LSB of the expression changed to 0.
> > Otherwise, it returns false.
> > 
> > - $stable returns true if the value of the expression did 
> not change.
> > Otherwise, it returns false.
> > 
> > When these functions are called at or before the first 
> clock tick of the
> > clocking event, the results are computed
> > 
> > by comparing the current sampled value of the expression to X.
> > 
> > =20
> > 
> > while according to the formal semantics (annex F.4), all 
> these functions
> > return false when called before the first tick of the 
> clocking event.
> > 
> > =20
> > 
> > Thanks,
> > 
> > Dmitry
> > 
> > 
> 
> -- 
> 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 Tue May 29 07:54:08 2007

This archive was generated by hypermail 2.1.8 : Tue May 29 2007 - 07:54:13 PDT