From: Adam Krolnik (krolnik@lsil.com)
Date: Thu Oct 12 2000 - 14:40:38 PDT
Good afternoon;
<p>Here are my recommendations. Most are considered typo's. There was
one without a recommendation from me.
<p> Adam Krolnik
Verification Mgr.
LSI Logic Corp.
Plano TX. 75074
Here are my recommendations on these comments. Thank you James,
for the concise set of codes on your comments. I will follow your
style in marking these comments. The coding is below for reference.
NO CHANGE
No change should be made.
SENSIBLE
Indicates that the change is a sensible one. However, it is not
strictly necessary, so if we are trying to minimize the number of
edits in this draft, we may choose to ignore it.
CLARIFICATION
A change which clarifies the standard and which should be implemented.
FIXTYPO
A change which is typographical or layout-like in nature. These
should be implemented.
UNSURE
I am not sure of the correct disposition.
********** COMMENTS **********
AnneH-TC-13) On page 338, note 1 says that part of a vector cannot be
dumped to a VCD file. However, on page 342, item c), it says that an
individual bit of a vector can be dumped. If bit-selects of a vector are
allowed, but part-selects are not, this should be stated clearly in one
place and not split across two different sections of the document.
CLARIFICATION:
Delete note 1 from 338. Replace item C, page 342 with
Part selects shall not be dumped separately, only bit selects or the
entire scalar or vector may be dumped.
<p>AnneH-TC-14) On page 634, in Figure 25-6, node_ms_index, node_ls_index,
node_lhs_element, and node_rhs_element are declared. On page 636, at the
end of the page, node_ms_element, node_ls_element, node_lhs_index, and
node_rhs_index are referred to. According to Annex F, the names in Figure
25-6 are correct, and page 636 is wrong.
FIXTYPO
<p><p>AnneH-EC-1) On page 16, "parallel" is spelled "paralee" the first three
times that it is used.
<p> FIXTYPO
<p>AnneH-EC-2) On page 16, the two cases in example 3 appear to be identical.
What was supposed to be different?
CLARIFICATION:
Add "=1" after the attribute name to the second part of example 3
(to follow the style of the previous examples.)
AnneH-EC-3) On page 24, "delay2" is declared but it isn't used.
<p> CLARIFICATION:
Strike 'delay2' from the box.
<p><p>AnneH-EC-4) On page 70, in section 5.6.3, change "(or if it returns
immediately" to "(it returns immediately".
<p> SENSIBLE
Strike 'or if'
<p>AnneH-EC-5) On page 84, in example 3, the declaration of "in" in the module
busdriver should be "busin".
FIXTYPO
<p>AnneH-EC-6) On page 84, in example 4, setting the default value for the
parameter bits to "1" creates an uninteresting row of just one flip flop.
It might be better to choose a different default number.
NO CHANGE: This is a standard default for parameterized elements.
[ This is not a good example because it is wasteful of simulation
time. A more complex element being replicated in an array would be
better.]
AnneH-EC-7) On page 113, in the second paragraph in section 8.1.1,
"parenthesis" should be "parentheses".
<p> FIXTYPO
<p>AnneH-EC-8) On page 113, in section 8.1.2, it would be more clear if you
said "or as part of the output declaration, when using either the first or
second form". Also, the first occurrence of "output declaration" in this
sentence does not use an "_", but the second occurrence does - be consistent.
SENSIBLE
Strike "in either case"
Replace "_" with space in output_declaration
<p>AnneH-EC-9) On page 114, in section 8.1.4, it would be clearer if the last
sentence were worded "It is illegal to have the same combination of inputs,
including edges, produce different outputs", or "It is illegal to have the
same combination of inputs, including edges, result in different outputs".
Or yet another approach would be "It is illegal to specify exactly the same
combination of all table inputs, including edges, in more than one table
entry in a UDP".
SENSIBLE
Replace "specified for different" with "produce different"
<p>AnneH-EC-10) On page 125, change "reg_lvalue" in the first paragraph (two
occurrences) to "variable_lvalue" to be consistent with Syntax 9-1.
FIXTYPO
AnneH-EC-11) On page 126, change 3 occurrences of "reg_lvalue" to
"variable_lvalue".
FIXTYPO
AnneH-EC-12) On page 130, in section 9.3.1, change "reg" to "variable".
FIXTYPO
AnneH-EC-13) On page 131, the last sentence in section 9.3.1 seems out of
place. "If either operand to an arithmetic operator is real, the resulting
expression is of type real" doesn't seem to have anything to do with the
discussion of the assign and deassign statements.
CLARIFICATION:
Strike sentence.
<p>AnneH-EC-14) On page 131, in section 9.3.2 paragraph 2, change "(as would a
net that is forced)" to "(as would a net that is assigned)".
UNSURE
<p>AnneH-EC-15) On page 158, in the example showing the second form of a task
declaration, remove the ";" after my_task. A semicolon should not separate
the task name from the port declarations inside the parentheses in the
second form.
FIXTYPO:
Strike ';' on second task definition.
<p>AnneH-EC-16) On page 161, in the fourth paragraph, the wrong bolding is
used. "endfunction keyword" should be "endfunction keyword".
FIXTYPO:
Bold 'endfunction'
Normalize 'keyword'
<p>AnneH-EC-17) On page 165, the third paragraph starts off with "Either form
of disable statement". I only see one form described in Syntax 11-1.
CLARIFICATION:
Replace 11-1 w/
disable_statement ::= disable hierarchical_task_identifier
| disable hierarchical_blobk_identifier
<p>AnneH-EC-18) On page 183, in section 12.2 in the first paragraph, "This
first in the module_parameter_port_list" should be "The first is the
module_parameter_port_list".
<p> FIXTYPO:
<p>AnneH-EC-19) There are two pages 203 and two pages 204.
<p> UNKNOWN: PDF does not have this problem!
<p>AnneH-EC-20) On page 210, in section 13.4.1, "and map it into" should be
"and maps it into".
FIXTYPO
<p>AnneH-EC-21) On page 219, in the fourth paragraph of section 14.2.3, the
description of path destinations could be made clearer.
>"For parallel connections (=>), the destination shall be any scalar output
or inout port or one of its bit-selects" could change to "For parallel
connections (=>), the destination shall be any scalar output or inout port
or the bit-select of a vector output or inout port".
>"For full connections (*>), the destination shall be a list of one or more
of the vector or scalar output and inout ports, and bit-selects or
part-selects of those ports" could change to "For full connections (*>),
the destination shall be a list of one or more of the vector or scalar
output and inout ports, and bit-selects or part-selects of vector output
and inout ports".
<p> SENSIBLE:
AnneH-EC-22) On page 237, in section 14.6.4.2 in paragraph 4, "It is an
error if a a module path" has an extra "a" in it.
FIXTYPO:
<p>AnneH-EC-23) In the last paragraph on page 237, add "second" and "last" or
"third" designators. "The second waveform shows showcancelled behavior in
conjunction with on-event. The last waveform shows showcancelled behavior
in conjunction with on-detect".
CLARIFICATION:
Add "second" and add "third to sentence 3 and 4 respectively."
<p>AnneH-EC-24) On page 259, in paragraph 2, change "$timeskew" to "$fullskew".
FIXTYPO:
AnneH-EC-25) On page 259, in case 2, "This transition at 'B'" should be
"This transition at 'C'".
FIXTYPO:
AnneH-EC-26) On page 296, in section 17.2.4, the wording is very awkward.
Try something like "Files opened using file descriptors may be read from,
only if they were opened with either the "r" or "r+" type values.
SENSIBLE:
<p>AnneH-EC-27) On page 296, in section 17.2.4.1 in the sentence beginning
with "Care should be taken", the word "return" is used three times. This
sentence is very awkward. Try something like "Care should be take to define
the width of the reg which gets the return value of $fgetc to be wider than
8 bits. This allows EOF (-1) to be read from the reg as 0xff in the event
of an error."
SENSIBLE:
<p>AnneH-EC-28) On page 297, in the paragraph starting with "Both functions
read" near the top of the page, there is a plural/singular agreement
problem. Should be "Both functions read characters, interpret them
according to a format, and store the results".
FIXTYPO:
AnneH-EC-29) On page 298, should the 'z' format get its own section? It is
currently described in the 'u' section.
TYPO:
The sixth paragraph under the 'u' section is the start of the 'z' format.
Add the letter 'z' in the correct column to this paragraph.
<p>AnneH-EC-30) On page 325, the code for the poisson distribution is shown
twice. The code for the chi_square distribution appears on page 325, but a
partial duplicate also appears on page 326.
TYPO:
Remove the last 3 lines on page 325.
Remove the lines on page 326 up to but not including
static double
t(seed, deg_of_free)
AnneH-EC-31) On page 328, at the end of the second paragraph, change
"remainding" to "remaining".
<p> FIXTYPO:
AnneH-EC-32) On page 342, item c), "The individual bits of vector nets can
be dumped individually" could be better worded as "A bit-select of a vector
net can be dumped".
NO CHANGE - fixed by a previous comment.
This archive was generated by hypermail 2.1.4
: Mon Jul 08 2002 - 12:54:14 PDT
and
sponsored by Boyd Technology, Inc.