RE: [sv-ec] Conflict due to range and packed_dimension


Subject: RE: [sv-ec] Conflict due to range and packed_dimension
From: Brad Pierce (Brad.Pierce@synopsys.com)
Date: Tue Sep 09 2003 - 10:02:55 PDT


Or maybe they are the same.

I did not notice the unusual Footnote 9, which says that packed_dimension
is context-dependent. Specifically, it says "Open-array ([]) form shall
only be used with dpi_proto_formal".

In my opinion, this footnote is another erratum. The desired effect
should be achieved with standard BNF, not with a footnote and
context-dependency.

-- Brad

-----Original Message-----
From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org]On Behalf Of Brad
Pierce
Sent: Tuesday, September 09, 2003 9:43 AM
To: kausikd@interrasystems.com
Cc: sv-ec@eda.org
Subject: Re: [sv-ec] Conflict due to range and packed_dimension

Yes, if the existing rules in the BNF were to be believed, then

       { packed_dimension } [ range ]

would be equivalent to

       { packed_dimension }

But the existing rules for packed_dimension and range in A.2.5 are
not actually the same. Consider, for example, the rules
for range_or_type in A.2.6, which, unlike those for packed_dimension,
do not generate the phrase "[]".

-- Brad

-----Original Message-----
From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org]On Behalf Of
Kausik Datta
Sent: Tuesday, September 09, 2003 4:55 AM
To: sv-ec
Subject: [sv-ec] Conflict due to range and packed_dimension

Hi,

The following rule has both packed_dimension and range non-terminals.

BNF sec A.2.2.1

data_type ::=
    integer_vector_type [ signing ] { packed_dimension } [ range ]

But rules for packed_dimension and range in sec A.2.5 are same.

Do we really need [range] at all in the BNF? Instead of that we can use
only packed_dimension.
Few other related rules also have the similar problem.

Thanks
Kausik



This archive was generated by hypermail 2b28 : Tue Sep 09 2003 - 10:04:27 PDT