RE: errata/634: 3.11.1: When is a parameter not a parameter

From: Bineet SRIVASTAVA (bineet.srivastava@st.com)
Date: Tue Nov 16 2004 - 21:30:00 PST

  • Next message: Shalom.Bresticker@freescale.com: "Re: errata/634: PROPOSAL - 3.11.1: When is a parameter not a parameter"

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

    From: Bineet SRIVASTAVA <bineet.srivastava@st.com>
    To: "'Steven Sharp'" <sharp@cadence.com>, <etf-bugs@boyd.com>
    Cc: "Bineet SRIVASTAVA" <bineet.srivastava@st.com>
    Subject: RE: errata/634: 3.11.1: When is a parameter not a parameter
    Date: Wed, 17 Nov 2004 11:03:17 +0530

     I fully agree with steven for the rule regarding parameters becoming
     localparams when there is an ANSI-C style parameter header.
     
     think, it can be resolved as
     * Allow parameter override for parameter declarations as a part of module
     declaration
     * Allow both(mixed) kind of parameter definitions as part of module
     declaration (extension to shalom's point); comma separated; in line with
     ANSI style port declarations.
     
     Any thoughts??
     bineet srivastava
     
     
     A module declaration may contain parameter definitions of
    > either type (or no parameter definitions), but not of both
    > types together in the same module declaration
     -----Original Message-----
     From: owner-etf@boyd.com [mailto:owner-etf@boyd.com] On Behalf Of Steven
     Sharp
     Sent: Wednesday, November 17, 2004 10:00 AM
     To: etf-bugs@boyd.com
     Subject: Re: errata/634: 3.11.1: When is a parameter not a parameter
     
     
     The following reply was made to PR errata/634; it has been noted by GNATS.
     
     From: Steven Sharp <sharp@cadence.com>
     To: etf-bugs@boyd.com, Brad.Pierce@synopsys.com
     Cc:
     Subject: Re: errata/634: 3.11.1: When is a parameter not a parameter
     Date: Tue, 16 Nov 2004 23:33:27 -0500 (EST)
     
      I must say that I thought the rule about parameters becoming localparams
     when there is an ANSI-C style parameter header was weird when I first came
     across it. I immediately tested our implementation and found that we had
     correctly implemented this rule. I would not have been surprised if we had
     not.
      
      I don't know how many users are using parameter declarations both places
     (and how many of those know that the ones inside the module are local
     parameters), but Neil is right about the potential for backward
     compatibility issues.
      
      In response to Brad's question, I tested our implementation and determined
     that this rule is only being applied to parameters at the module level.
     Parameters inside nested scopes are not being treated as localparams. I
     don't know how other implementations are treating it, but this is one data
     point.
      
      Steven Sharp
      sharp@cadence.com
      
     
     
     

    This archive was generated by hypermail 2.1.4 : Tue Nov 16 2004 - 21:30:08 PST and
    sponsored by Boyd Technology, Inc.