[sv-bc] BNF error in configuration use_clause

From: Bresticker, Shalom <shalom.bresticker@intel.com>
Date: Mon Mar 24 2014 - 00:27:15 PDT
Priya Khanna from Atrenta brought to my attention that there appears to be a BNF error in the syntax for use_clause parameter assignments in configurations.

All the examples show named parameter assignments enclosed in #(...), like this:

config cfgl;
design rtlLib.top;
instance top use #(.WIDTH(32));
instance top.a1 use #(.W(top.WIDTH));
endconfig

However, the BNF is

use_clause ::= use [ library_identifier . ] cell_identifier [ : config ]
| use named_parameter_assignment { , named_parameter_assignment } [ : config ]
| use [ library_identifier . ] cell_identifier named_parameter_assignment { , named_parameter_assignment } [ : config ]


and named_parameter_assignment is

named_parameter_assignment ::= . parameter_identifier ( [ param_expression ] )

It looks to me like the syntax used in use_clause should have been parameter_value_assignment:

parameter_value_assignment ::= # ( [ list_of_parameter_assignments ] )

list_of_parameter_assignments ::=
ordered_parameter_assignment { , ordered_parameter_assignment }
| named_parameter_assignment { , named_parameter_assignment }

ordered_parameter_assignment ::= param_expression
named_parameter_assignment ::= . parameter_identifier ( [ param_expression ] )

with maybe a footnote that only named_parameter_assignments are allowed in use_clauses and not ordered_parameter_assignments.

How did we miss that?

Shalom Bresticker
Communications & Storage Infrastructure Group Design Automation
Intel Jerusalem, Israel
+972  2 589 6582 (office)
+972 54 721 1033 (cell)
http://www.linkedin.com/in/shalombresticker
The devil is in the details.

---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Mon Mar 24 00:27:32 2014

This archive was generated by hypermail 2.1.8 : Mon Mar 24 2014 - 00:27:48 PDT