BTF Errata errors in Draft 3

From: Anders Nordstrom (andersn@nortelnetworks.com)
Date: Sat Oct 09 1999 - 11:09:47 PDT

Next message: Anders Nordstrom: "REMINDER: BTF Conference Call"
Previous message: Michael McNamara: "Re: Ambiguity in $fopen description"
Next in thread: Shalom Bresticker: "Re: BE55"
Reply: Shalom Bresticker: "Re: BE55"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

<x-html>
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<body text="#000000" bgcolor="#FFFFFF" link="#0000FF" vlink="#FF0000" alink="#000088">
Cliff,
I have gone through all the BTF errata passed by the 1364 WG to make
sure they
 are corrected in Draft 3. Most of them are corrected but not all of
them. Below is
 a list of the incorrectly implemented or missing BTF errata in Draft
3 plus a few more
 that I found along the way. All errata not in the list below are OK.
 
<ul>
<li>
BE7 - The syntax for timing_check_condition in Syntax 15-14 is different
than in 
A.7 on page 741. 
 </li>

<li>
BE8 - The syntax for real number on page 793 is incorrect. The "1"
refers to note 1, 
it should not be part of the syntax. 
 </li>

<li>
BE18 - page 179 section 12.4 at the end of the second paragraph:
"See section ???" 
should be "See section 10.2.1 and 10.3.1" 
Figure 12-2 on page 181: move the second column an inch
to the right. 
The following text from BE18 is missing on page 182 after the example: 
 
 The name of a module or module instance is sufficient to identify
the module and its location in the hierarchy. A lower-level module can 
reference items in a module above it in the</li>

hierarchy. For variables they can be referenced if the name of the
higher-level module or its instance name is known. For tasks, 
functions and named blocks, Verilog will look in the
 enclosing module for the name, until it is found or until the root
of the hierarchy is reached. It will only search in higher enclosing modules 
for the name, not instances. The syntax for a
 hierarchical reference is as follows:
 
 <name_of_module_or_instance>.<name_of_item>
 
 There can be no spaces within the reference, except for escaped
identifiers embedded in the hierarchical name reference,. 
Example 12-11 demonstrates upward referencing. In this
 example, there are four modules, mod_a, mod_b, mod_c and mod_d.
Each module contains an integer x. 
The highest level modules in this segment of a model hierarchy are mod_a
and
 mod_d. There are two copies of module mod_b.x because both mod_a
and mod_d both instantiate mod_b.X. 
There are four copies of mod_c.x because each of the two copies of
 mod_b.x instantiates mod_c.x twice. }
 
On page 183, the last line in the third paragraph of 12.5. The line should
be: 
 
 a module boundary is encountered. {If the item is a variable, it
will stop at a module
 boundary; if the item is a task, function, or named block it continues
to search higher-level modules until found.} 
The search {for variables} shall cross named block, task and function
 boundaries but not module boundaries. 
 
The following section of text is missing after the first paragraph
on page 184:
 
If an identifier is referenced with a hierarchical name, the path can
start with an module name, instance name, task, function, 
or named block. The names will be searched first at the
 current level, then in higher-level modules until found. Since both
module names and instance names can be used, 
precedence is given to instance names if there is a module named
 the same as an instance name. 
 
 
<li>
BE24 - In the fourth paragraph of section 12.2.1 on page 170.
The second sentence should be: "When defparams are encountered in 
multiple source files, e.g. found by library searching,
the defparam...... 
 </li>

<li>
BE31 - Syntax 6-1 on page 64. Last line of net_declaration syntax
should be: 
list_of_net_decl_assignments. (decl typed dcl). 
 </li>

<li>
BE39 - Last paragraph of section 10.2.1 on page 144. The reference
on the first line should be "(see 12.3.2 and 3.2.2)" 
 </li>

<li>
BE41 - Syntax 9-4 on page 121 is not the same as in A.6. Syntax
9-6 is missing "attribute" see page 737. 
Syntax 9-10 on page 131 should be "hierarchical_event_identifier". 
Syntax 11-1 on page 151 is missing "hierarchical", see
page 738 
 </li>

<li>
BE52 - Section 3.2.2 on page 18. The following sentence is missing:
" The default initialization 
value for real and realtime reg datatypes shall be 0.0".
It should follow the sentence: 
The default initialization value for a reg datatype...... 
 </li>

<li>
BE55 - This one doesn't seem to be implemented at all.... 
Replace the first paragraph in section 3.5 on page 21
with: 
 
The syntax shown in Section 3.2 shall be used to declare nets and registers
explicitly. In the absence of an explicit declaration, 
an implicit net of default net type shall be assumed in the following circumstances:</li>

 - If an identifier is used in a port expression declaration,
then an implicit net of type wire shall be assumed, with the vector width
of 
the port expression declaration. See Section 12.3.2 for a discussion of
port expression declarations.
- If an identifier is used in the terminal list of a primitive instance
or a module instance, and that identifier has not been
 explicitly declared previously in one of the declaration statements
of the instantiating module, then an implicit scalar net of 
default net type shall be assumed. 
 
Section 12.3.2 on page 173: change the second word "port" to "port_expression"
. 
 
In section 12.3.2 on page 174. Chage the sentence "A port can be declared
in both a port declaration and a net or register declaration. 
If a port is declared as a vector, the range specification
between the two declarations of a port shall be identical. " to: 
 
A port_expression which is an identifier can be declared in both a port
declaration and a net or register declaration. A net or register 
declaration establishes the data type of the
 internal net or register connected to the port. If no net or register
declaration is made for the port_expression identifier, 
then a default data type is assumed.
An explicit net or register declaration for an identifier which is
also used in a port_expression declares the specific data type 
and vector size of the port_expression. If the vector
 range of a data type declaration differs from the vector range of
a port_expression declaration for the same identifier, 
the declaration of the net or register shall be used.
If there is no explicit net or register declaration for an identifier
used in a port_expression declaration, then an implicit net shall be assumed, 
with the vector width of the port_expression declaration. The implicit
net data type shall be wire, unless another default type has been directed. 
See Section 19.2 for a discussion of control of the type for implicitly
 declared nets using the `default_nettype compiler directive. This
implicit net type shall be used for the internal net type when the rules 
for connecting dissimilar ports are applied.
 These rules are discussed in Section 12.3.6 and Section 12.3.8. 
 
 
<li>
BE57 - Section 4.2.3.1 on page 51. Remove extra white space in "8*n
bits" 
 </li>

<li>
BE59 - Sectoin 4.4.2 on page 55. Several typos in the example. 
 (ab) should be (a&b) 
 emdmodule should be endmodule 
 ab in the text following the example should be a&b
(two places) 
 </li>

<li>
BE63 - Section 9.7.7 examples on page 134. 
The comments under "repeat (-3)" and "repeat (a)" should
be moved to the right hand side of the page 
to make the example easier to follow. 
 </li>

<li>
BE71 - In A.4 page 734. Change "list_of_module_connections" to "list_of_port_connections" 
In the example on page 174. Align all the comments under
the module declarations in one column 
towards the right side of the page. 
 </li>

<li>
BE74 - This one is not implemented in the BNF. Section A.8 page
741. 
 Replace all occurences of "multiple_concatenation" with
"replication". 
 Replace the definition of multiple_concatienation with
the definition of replication: 
 <tt>replication ::= {constant_expresson concatenation
}</tt> 
 </li>

<li>
BE82 - This is not implemented in the BNF section A.8 on page 743. 
Replace "size" with "non_zero_size" in the syntax for
decimal, binary, octal and hex number. 
Add the following syntax: 
 
non_zero_size ::=</li>

non_zero_unsigned_number
non_zero_unsigned_number ::=
 
non_zero_decimal_digit { _ | decimal_digit}
non_zero_decimal_digit ::=
 
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
 
 
<li>
BE83 - The Note in section 9.2 on page 114. 
 The text is not correct, it should be: 
 
 When the right-hadn side evaluates to fewer bits
than the left-hand side, then if the right-hand side 
 is signed (see Section 4.5), it shall be sign-extended
to the size of the left-hand side. 
 </li>

<li>
BE84 - Section 3.12 page 32. In the third paragraph, add one white
space before the word "Once". 
Section 12.3.4 on page 175. Add the following sentence: 
"Once a port is connected by name, there shall not be
another named port connection for this port" 
 </li>

<li>
BE86 - In Table 4-5 on page 39. Change "multiply" to "multiplied"
and 
change "divide" to "divided" 
 </li>

<li>
BE90 - Section 4.4.3 on page 55. Align the comments under simulator
output with the ones above. 
 </li>

<li>
BE91 - Annex A page 742. The syntax for regl_value is missing "real_identifier" 
 </li>

<li>
Note 2 in the BNF section, page 746 need some meaningful text or should
be removed. 
 </li>

<li>
The "box" around Syntax 15-1, 15-2 through 15-12 on pages 224 to 237 are
missing. 
 </li>

<li>
Section 3.2.2 page 18. Typo in the middle of the first paragraph: "shall
be he unknown" should 
be "shall be the unknown" 
 </li>

<li>
Example 1 and 2 on pages 158 and 159: 
Align all the comments in one column towards the right
hand side of the page to make them easier to read.</li>
</ul>

Regards,

Anders
</body>
</html>

</x-html>

Attachment Converted: "C:\Documents and Settings\stefen\Application Data\Qualcomm\Eudora\andersn14.vcf"

Next message: Anders Nordstrom: "REMINDER: BTF Conference Call"
Previous message: Michael McNamara: "Re: Ambiguity in $fopen description"
Next in thread: Shalom Bresticker: "Re: BE55"
Reply: Shalom Bresticker: "Re: BE55"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Mon Jul 08 2002 - 12:53:30 PDT and
sponsored by Boyd Technology, Inc.