Re: enhancement/17: 12.1.3 is not clear enough about permitted defparam usage

From: Shalom.Bresticker@freescale.com
Date: Wed May 05 2004 - 02:20:00 PDT

  • Next message: Shalom.Bresticker@freescale.com: "Re: errata/113: generate"

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

    From: Shalom.Bresticker@freescale.com
    To: etf-bugs@boyd.com
    Cc:
    Subject: Re: enhancement/17: 12.1.3 is not clear enough about permitted
     defparam usage
    Date: Wed, 5 May 2004 12:39:13 +0300 (IDT)

     Does the current generate proposal (errata/113) cover this issue?
     
     Shalom
     
     
     On Mon, 13 Aug 2001 Shalom.Bresticker@motorola.com wrote:
     
    > 12.1.3 says (para. 7),
    >
    > "a defparam statement within the generate scope or within a
    > hierarchy instantiated within the generate scope shall only
    > modify the value of a parameter declared within the generate
    > scope or within a hierarchy instantiated within the generate
    > scope."
    >
    > It is unclear whether a defparam may reference a different
    > iteration of a generate loop.
    >
    > E.g.,
    > genvar i;
    >
    > generate for(i=0; i < 8; i = i+1)
    > begin : somename
    > flop my_flop(in[i], in1[i], out1[i]);
    > defparam somename[i+1].my_flop.xyz = i ;
    > end endgenerate
    >
    > There have been different interpretations of whether this is
    > permitted or not.
    > This must be clarified.
     

    This archive was generated by hypermail 2.1.4 : Wed May 05 2004 - 02:20:05 PDT and
    sponsored by Boyd Technology, Inc.