From: Shalom.Bresticker@motorola.com
Date: Sat Sep 20 2003 - 11:50:01 PDT
Precedence: bulk
The following reply was made to PR errata/226; it has been noted by GNATS.
From: Shalom.Bresticker@motorola.com
To: Brad.Pierce@synopsys.com
Cc: etf-bugs@boyd.com
Subject: Re: errata/226: PROPOSAL - Illegal to assign mintypmax expression
to parameter?
Date: Sat, 20 Sep 2003 22:35:21 +0300 (IDT)
I oppose the proposal.
We have already concluded that the BNF is faulty and does not correctly
describe the tool behaviors, which allow the so-called illegal cases.
Similarly, the statement that
"Specparams allow the use of mintypmax_expression but parameter declarations do
not" is not correct.
At the Aug. 11 ETF meeting, we rejected an identical proposal.
Shalom
> APPEND the following line to the examples at the end
> of 3.11.1
>
> parameter p = (1:2:3); //parenthesis required since constant_mintypmax_expression is not allowed
>
> Answer to original question: The behavior is correct as described. Section 3.11.3 describes the difference between parameters and specify parameters and it states that a specify parameter is a special type of parameter intended only for providing timing and delay values. Specparams allow the use of mintypmax_expression but parameter declarations do 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, which includes (constant_mintypmax_expression), hence example m_legal is OK but m_illegal is not.
--
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
: Sat Sep 20 2003 - 11:52:36 PDT
and
sponsored by Boyd Technology, Inc.