Re: errata/654: 14.2.3: specify block edge-sensitive path description with polarity

From: Shalom.Bresticker@freescale.com
Date: Thu Mar 03 2005 - 13:20:00 PST

  • Next message: Shalom.Bresticker@freescale.com: "Re: errata/655: 2005D6, 7.1.6: ambiguities in instance array port connection rules"

    The following reply was made to PR errata/654; it has been noted by GNATS.

    From: Shalom.Bresticker@freescale.com
    To: Steven Sharp <sharp@cadence.com>
    Cc: etf-bugs@boyd.com
    Subject: Re: errata/654: 14.2.3: specify block edge-sensitive path description
     with polarity
    Date: Thu, 3 Mar 2005 23:32:37 +0200 (IST)

     I agree that in practice the simulators ignore the polarity operator.
     
     In principle, a different type of tool might relate to it.
     
     Again, the problem is that it is not allowed by the BNF, but some people
     do write that way, and the simulators do accept it, but not all tools.
     
     Shalom
     
     
     On Thu, 3 Mar 2005, Steven Sharp wrote:
     
    >
    > >But all 3 simulators that we have accept the code as written by our memory
    > group,
    > >who are apparently used to writing it that way all the time.
    > >
    > >Should this syntax be legal? What does it mean?
    >
    > I would guess that the simulators are completely ignoring the +. Even
    > for simple delay path descriptions, it has no effect on the behavior of
    > a simulator. The tools probably throw it away as soon as they see it,
    > without worrying about what kind of path this is.
    >
    > Steven Sharp
    > sharp@cadence.com
    >
     
     --
     Shalom Bresticker Shalom.Bresticker @freescale.com
     Design & Verification Methodology Tel: +972 9 9522268
     Freescale Semiconductor Israel, Ltd. Fax: +972 9 9522890
     POB 2208, Herzlia 46120, ISRAEL Cell: +972 50 5441478
       
     [ ]Freescale Internal Use Only [ ]Freescale Confidential Proprietary
     

    This archive was generated by hypermail 2.1.4 : Thu Mar 03 2005 - 13:20:12 PST and
    sponsored by Boyd Technology, Inc.