From: Shalom Bresticker (Shalom.Bresticker@motorola.com)
Date: Mon Aug 26 2002 - 09:38:22 PDT
Precedence: bulk
-------- Original Message --------
Subject: enhancement/17: 12.1.3 is not clear enough about permitted
defparam usage
Date: Mon, 13 Aug 2001 04:53:00 -0700
From: Shalom.Bresticker@motorola.com
Reply-To: btf-bugs@boyd.com
To: btf@boyd.com
Precedence: bulk
>Number: 17
>Category: enhancement
>Originator: Shalom.Bresticker@motorola.com
>Description:
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
: Thu Oct 10 2002 - 09:24:28 PDT
and
sponsored by Boyd Technology, Inc.