From: Adam Krolnik (krolnik@lsil.com)
Date: Wed Dec 15 1999 - 08:34:44 PST
Good morning all;
Here is an unordered list of requests.
Adam Krolnik
Verification Mgr
LSI Logic Inc.
Plano TX. 75074
972-244-5124
-------------------------------------------------------------------
Was:
Section 19.7 `line, last sentence of paragraph 2.
"The level parameter indicates whether an include file has
been specified (value is 1), an include file is exited (value is 2),
or neither has been done (value is 0).
Proposed:
"The level parameter indicates whether an include file has
been entered (value is 1), an include file is exited (value is 2),
or neither has been done (value is 0).
<p>Proposed change:
Switch 'specified' to 'entered' - removes ambiguity.
---------------------------------------------------------------
Section 17.1.1.2 Format specifications
Was:
Proposed:
Add the %l format specified as defined in section 13.6 to
the table in this section.
Remove the VPI discussions as this should also be in the
relevant VPI section.
---------------------------------------------------------------
Section 17.10.2 $value$plusargs()
I submitted a draft change request with extra examples/more text.
Has this not been incorporated, or is it lost?
---------------------------------------------------------------
Section 13.2.1 Specifying libraries.
Was
library rtlLib "/*.v"; // match all files in the current directory with
a .v suffix.
Proposed:
library rtlLib "*.v"; .....
Proposed change. Remove the erroneous '/' to indicate the current
directory.
---------------------------------------------------------------
Section 4.1.5 Arithmetic operators
Was: >> Need more here re: pow <<
Proposed:
Remove text, complete work...
---------------------------------------------------------------
Section 2.8 Attributes
Was:
See the syntax at the end of this section for a list of statements that
may have attributes attached to them.
Proposed:
See the syntax box ... ?!
Syntax 2-3 Statements with attributes attached.
module declarations
module or generate item
inout declaration
input declaration
output declaration
integer declaration
net declaration
reg declaration
time declaration
[ Note, no real, realtime, event or genvar declarations.]
function declaration
task declaration
block reg declaration
gate instantiation
module instantiation
ordered port connection
named port connection
udp declaration
udp output declaration
udp input declaration
initial construct
always construct
par(allel) block
seq(ential) block
conditional statement
if else if statement
case statement
[Note, no looping statements]
task call
function call
unary operator
binary operator
conditional operator
Proposed change:
Add missing table referred to in the text.
------------------------------------------------------------
Section 2.8 Attributes
Was:
Proposed:
case item
statement
Proposed change:
Add attribute_instance to case items, and as an element of statement.
You can't specify an attribute for an item of a case statement. What
if I wanted to attach (* rtl_not_reached *)
Also, you can't specify an attribute next to a statement within
sequential blocks. What if I wanted to say
(* rtl_ignore_width_mismatch *)
a = {a,b};
An attribute_instance is a valid item of a module, why not of
statements?
BNF:
tatement ::=
<current>
attribute_instance
<p>case_item ::=
expression {, expression}: [attribute_instance] statement_or_null
| default [:] [attribute_instance] statement_or_null
This archive was generated by hypermail 2.1.4
: Mon Jul 08 2002 - 12:53:31 PDT
and
sponsored by Boyd Technology, Inc.