From: Dennis Marsa (drm@xilinx.com)
Date: Fri Jul 19 2002 - 13:06:14 PDT
Precedence: bulk
Michael McNamara wrote:
>
> Passing out the issues:
>
> ISSUE State Originator Arrival-Date Synopsis
> ---Dennis-----------------------------------------------------------------------------------
> 15 open Sashi Obilisetty 2001-08-12 19.4: typo + confusing
> 16 open Shalom.Bresticker@motorola.com 2001-08-12 19.7 `line - meaning of level
> parameter is unclear
> 18 open Stefen Boyd 2001-08-16 Table 4-1 missing arithmetic
> shift operators
> 19 open "Anders Nordstrom" 2001-08-17 Incorrect concatenation
> operator description
> Your tasks are:
>
> 1: Classify difficulty: easy/hard
> 2: Identify Sections/table number/figure number affected
> 3: Modify subject to make the issue clearer
> 4: (optionally) provide link to relevant URL archive on boyd.com
Here are the classifications for the errata that were assigned to me.
Regards,
Dennis Marsa
Xilinx, Inc.
>> ----------------------------------------------------------------------
>> Reporter's email: Shalom.Bresticker@motorola.com
>> Number: 15
>> Category: errata
>> Synopsis: 19.4: typo + confusing
>> Originator: Sashi Obilisetty <sashi@dualsoft.com>
>> Release: IEEE 1364-2001
>> Description: 18. Addtl cond compilation (`ifndef, `elsif, `undef)
>> (Section 19.4)
>>
>> - Typo on page 363 (line 13 from the bottom); 2 consecutive "the"s
>> - There should be better indentation for the sections that
>> describe how the compiler directives work. I suggest the following
>> change on Page 363 (and a similarly indented change for the
>> corresponding section on Page 364).
>>
>> - When an `ifdef is encountered, the ifdef text macro
>> .....
>> - If the ifdef text macro is defined ...
>> - If the ifdef test macro has not been defined, ...
>> o If there is an `elsif compiler directive, ...
>> o If the elsif text macro is defined,..
>> o etc, etc
>> ----------------------------------------------------------------------
Difficulty: easy (but possibly hard)
Section: 19.4, pg 354-355 (or 367-368 of PDF)
Better Synopsis: Section 19.4: Conditional compilation directives description unclear
Archive URL: http://www.boydtechinc.com/btf/archive/btf_2001/1445.html
Recommendation: adopt
- Easy fix: The double "the the" is still there on page 354 and is an easy fix.
- Hard fix: The indentation structure of the algorithmic descriptions of how
these directives could indeed be improved. However, this might be considered
a low priority issue compared to some other errata. If worth rewording this
should be reclassified as a "hard" errata.
>> ----------------------------------------------------------------------
>> Reporter's email: Shalom.Bresticker@motorola.com
>> Number: 16
>> Category: errata
>> Synopsis: 19.7 `line - meaning of level parameter is unclear
>> Originator: Shalom.Bresticker@motorola.com
>> Release: IEEE 1364-2001
>> Description: In 19.7 (`line): "The level parameter indicates whether an
>> include file has been entered (value is 1), an include file
>> is existed (value is), or neither has been done(value is 0)."
>>
>> This sentence is incomprehensible to me.
>>
>> At the very least, an example or examples must be added.
>> ----------------------------------------------------------------------
Difficulty: hard
Section: 19.7, pg. 358 (or 371 of PDF)
Better Synopsis: Section 19.7: `line - meaning of level parameter is unclear
Archive URL: http://boydtechinc.com/btf/archive/btf_2001/1446.html
Recommendation: needs consideration by group
>> ----------------------------------------------------------------------
>> Reporter's email: stefen@boyd.com
>> Number: 18
>> Category: errata
>> Synopsis: Table 4-1 missing arithmetic shift operators
>> Originator: Stefen Boyd <stefen@boyd.com>
>> Release:
>> Description:
>> Table 4-1 should have arithmetic operators
>> '>>>' and '<<<' on page 63 of 1364/D6:
>>
>> Was:
>> i op j, where op is:
>> >> << **
>>
>> Proposed:
>> i op j, where op is:
>> >> << >>> <<< **
>> ----------------------------------------------------------------------
Difficulty: easy
Section: 4.4.1, pg. 60 (or 73 in PDF), Table 29
Better Synopsis: Section 4.4.1, Table 29: Arithmetic shift operators missing
Archive URL: http://www.boydtechinc.com/btf/archive/btf_2001/1464.html
Recommendation: adopt
- Obvious omission.
- Note: What apparently was Table 4-1 is now Table 29.
>> ----------------------------------------------------------------------
>> Reporter's email: andersn@nortelnetworks.com
>> Number: 19
>> Category: errata
>> Synopsis: Incorrect concatenation operator description
>> Originator: "Anders Nordstrom" <andersn@nortelnetworks.com>
>> Release:
>> Description: One of the examples under $random on page 322 show:
>> rand = {$random} %60;
>> This example works both in Verilog-XL and VCS.
>>
>> This is legal according to the BNF in section A.8.1 since it
>> allows one or more expressions.
>> concatenation ::= {expression {,expression}}
>>
>> In section 4.1.14 it says:
>> A concatenation is the joining together of bits
>> resulting from two or more expressions.
>>
>> This is inconsistent with the example on page 322 and
>> with the BNF.
>>
>> What does concatenation of one expression mean?
>>
>> Proposal: Add text in section 4.1.14 explaining what {expression}
>> does and provide an example.
>>
>> Regards,
>>
>> Anders
>> ----------------------------------------------------------------------
Difficulty: easy (possibly hard)
Section: 4.1.14, pg. 51 (or 64 in PDF)
Better Synopsis: Section 4.1.14: Incorrect concatenation operator description
Archive URL: none found
Recommendation: adopt
- Easy fix: First sentence of section 4.1.14 could be changed to
say "one or more expressions" instead of "two or more expressions".
- Hard fix: Need new text for decribing the semantics of a concatenation
of one item and an example which is acceptable to the group.
This archive was generated by hypermail 2.1.4
: Thu Oct 10 2002 - 09:24:26 PDT
and
sponsored by Boyd Technology, Inc.