From: Shalom.Bresticker@motorola.com
Date: Sun Jun 22 2003 - 22:40:04 PDT
Precedence: bulk
The following reply was made to PR errata/226; it has been noted by GNATS.
From: Shalom.Bresticker@motorola.com
To: etf-bugs@boyd.com
Cc:
Subject: Re: errata/226: PROPOSAL - Illegal to assign mintypmax expression
to parameter?
Date: Mon, 23 Jun 2003 08:37:52 +0300 (IDT)
I do not accept that explanation.
Historically, specparams were only allowed in specify blocks.
Only in 1364-2001 were they allowed also outside of specify blocks.
Parameters were always allowed min:typ:max expressions.
The only question is about the parentheses.
As already pointed out, even the 1364-1995 tools allow them without parentheses
in certain situations.
Shalom
> Keep the existing behaviour. Section 3.11.3 describe the difference between
parameters and specify parameters and it states that specify parameters is a
special type of parameter intended only for providing timing and delay values.
Specparams allow the use of mintypmax_expression but parameter declarations
does not. Table 8 in section 3.11.3 is clearly stating that parameters may not
be assigned specparams so it is ok that they are declared differently.
> Parameters may be assigned constant_expressions which include constant_primary and
constant_primary include (constant_mintypmax_expression), hence example
m_legal is OK but m_illegal is not.
>
> Add the following line in the last example in section 3.11.1:
> parameter p = (1:2:3); //parenthesis required since constant_mintypmax_expression is not allowed.
> http://boydtechinc.com/cgi-bin/issueproposal.pl?cmd=view&pr=226
--
Shalom Bresticker Shalom.Bresticker@motorola.com
Design & Reuse Methodology Tel: +972 9 9522268
Motorola Semiconductor Israel, Ltd. Fax: +972 9 9522890
POB 2208, Herzlia 46120, ISRAEL Cell: +972 50 441478
This archive was generated by hypermail 2.1.4
: Sun Jun 22 2003 - 22:40:50 PDT
and
sponsored by Boyd Technology, Inc.