Tue Oct 4 01:00:44 2005 PST
| Release | Meaning |
|---|---|
| 2001a | Issue against 1364-2001 First Edition |
| 2001b | Issue against 1364-2001 Second Edition (Possibly also issue in First Edition) |
| 2001a, 2001b | Issue against both 1364-2001 First and Second Editions (i.e. errata partial fix in 2001b, but more changes required) |
| ISSUE | Release | Synopsis | Fix |
|---|---|---|---|
| 287 | 2001b
|
`compatibility - backward compatibility compiler directives
|
"Proposal to take 1800, 26.4 and make it 19.11 (omitting P1800-2005 version specifier), and update the cross-ref list at beginning of clause 19 to include `pragma, `begin_kewords and `end_keywords. Also remove any other references to SystemVerilog. Moved: Chas Second: Stu Approved Unanimously." |
| 465 | 2001b: 3.2.1, 3.2.2, 3.6
|
3.2, 3.6: net and variable initialization descriptions
|
Close this issue. It was dealt with in part 3 of the Fix to # 483. |
| 486 | 2001b: 12.3.3
|
12.3.3: Implicit nets are not necessarily unsigned
|
In 12.3.3, REPLACE Implicit nets shall be considered unsigned. Nets connected to ports without an explicit net declaration shall be considered unsigned, unless the port is declared as signed. WITH Nets connected to ports without an explicit net declaration shall be considered unsigned, unless the port is declared as signed. Other implicit nets (see 3.5) shall be considered unsigned. and REPLACE input [7:0] a; // no explicit declaration - net is unsigned WITH input [7:0] a; // no explicit net declaration - net is unsigned and REPLACE output [7:0] e; // no explicit declaration - net is unsigned WITH output [7:0] e; // no explicit net declaration - net is unsigned |
| 613 |
|
Incorrect specification of $removal (15.2.4)
|
To correct the issue, Table 15-4 on page 253 should be changed as follows: The description for reference event should be 'Timecheck event' and the description for data_event should be ' Timestamp event'. |
| 619 |
|
What is the width of a range with z and x's in the bounds?
|
In 3.3.1, REPLACE "The msb and lsb constant expressions may be any integer value -- positive, negative or zero." WITH "The msb and lsb constant expressions may be any integer values -- positive, negative or zero. It shall be illegal for them to contain any unknown (x) or high-impedance bits." In 3.9, REPLACE "The value of the constant expression can be a positive integer, a negative integer or zero." WITH "The constant expressions may be any integer values -- positive, negative or zero. It shall be illegal for them to contain any unknown (x) or high-impedance bits." |
| 645 | 2001b
|
7.1.2: pulldown strength specification ambiguity
|
In 7.1.2, CHANGE "The pullup gate can have only strength1 specification; strength0 specification shall be optional. The pulldown gate can have only strength0 specification; strength1 specification shall be optional. See 7.8 for more details." TO “The pullup gate shall have one of the following: no strength specification, only a strength1 specification, or both strength1 and strength0 specifications. The pulldown gate shall have one of the following: no strength specification, only a strength0 specification, or both strength1 and strength0 specifications. See 7.8 for more details."” |
| 646 | 2001b
|
"initial" and "always" "constructs"
|
Change all references to 'initial' and 'always' constructs to use the term 'construct' where another term such as 'block' was used. |
Hosted by Boyd Technology