From: Anders Nordstrom (Anders.Nordstrom.andersn@nt.com)
Date: Wed Nov 25 1998 - 14:07:26 PST
BAD MSG:
<x-html><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
HTML>
<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000FF" VLINK="#FF0000" ALINK="#000088">
Dear BTF Team,
Please review the enclosed new errata and we can discuss them on our
next conference call.
<BR>They may also be found on the 1364 Web site.
Regards,
Anders
<PRE>--
+-------------------------------------------------------------------------+
| Anders Nordstrom |
| Senior ASIC Designer |
| |
| Nortel Networks Email: andersn@nortelnetworks.com |
| P.O. Box 3511 Station C Phone: 613-763-9186 |
| Ottawa, Ontario K1Y 4H7 Fax: 613-763-2626 |
+-------------------------------------------------------------------------+</PRE>
</BODY>
</HTML>
</x-html><x-html><HTML>
<HEAD>
<TITLE> BE79 </TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF">
<BR>
<HR SIZE=5 NOSHADE>
<H2> BE79 - Draft 1 Errata - related to B19 </H2>
Content-Length: 27636
X-Lines: 626
X-Status: $$$$
X-UID: 0000000734
Status: RO
<TABLE BORDER COLS=2 WIDTH="75%" >
<TR><TD>
Section: </TD><TD> 2.5.1 & 4.1.12
</TD></TR><TR><TD>
Date Submitted: </TD><TD> 981117
</TD></TR><TR><TD>
Requestor: </TD><TD> Tom Fitzpatrick (tfitz@cadence.com)
</TD></TR><TR><TD>
Status: </TD><TD> Proposal
</TD></TR><TR><TD>
Analyzed by: </TD><TD> Tom Fitzpatrick
</TD></TR>
</TABLE>
<H3> Details and Proposal </H3>
Section: 2.5.1 <BR>
Page: 8
Note 1 should be changed to read: <BR>
"Sized negative numbers and sized signed numbers are sign-extended when
assigned to a register data type, regardless of whether the register itself
is signed or not."
Section: 4.1.12 <BR>
Page: 36
Add the following prior to the Examples:
"The result type of all shift operations shall be signed if and only if the
left-hand operand is signed. If the left-hand operand is unsigned, then the
result type of the shift operation shall be unsigned."
-Tom
<PRE>
---------------
Tom Fitzpatrick
Senior Technical Marketing Manager Cadence Design Systems, Inc.
Cycle Simulation Products 270 Billerica Rd.
Logic Design and Verification Business Unit Chelmsford, MA 01824
x6438 (978)446-6438
</PRE>
<HR SIZE=5 NOSHADE>
</BODY>
</HTML>
</x-html><x-html><HTML>
<HEAD>
<TITLE> BE80 </TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF">
<BR>
<HR SIZE=5 NOSHADE>
<H2> BE80 - B19 - Result type of Arithmetic Shift operator </H2>
<TABLE BORDER COLS=2 WIDTH="75%" >
<TR><TD>
Section: </TD><TD>
</TD></TR><TR><TD>
Date Submitted: </TD><TD> 980831
</TD></TR><TR><TD>
Requestor: </TD><TD> Tom Fitzpatrick (tfitz@cadence.com)
</TD></TR><TR><TD>
Status: </TD><TD> Submitted
</TD></TR><TR><TD>
Analyzed by: </TD><TD> TBD
</TD></TR>
</TABLE>
<H3> Details </H3>
Hi All,
It was pointed out to me by a colleague that the B19 proposal neglected to
specify the type of output supplied by the new arithmetic shift operator. I
would like to remedy that now.
I propose that the result of both arithmetic and logical shift operators
shall be the same type as the left-hand operand of the shift operation.
The other alternative is for arithmetic shifts to produce a signed result,
and logical shifts to produce an unsigned result, regardless of the operands.
At the moment, I'm really on the fence about this one. Any suggestions one
way or the other?
Thanks,<BR>
-Tom
<PRE>
---------------
Tom Fitzpatrick
Senior Technical Marketing Manager Cadence Design Systems, Inc.
Cycle Simulation Products 270 Billerica Rd.
Logic Design and Verification Business Unit Chelmsford, MA 01824
x6438 (978)446-6438
</PRE>
<HR SIZE=5 NOSHADE>
</BODY>
</HTML>
</x-html><x-html><HTML>
<HEAD>
<TITLE> BE81 </TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF">
<BR>
<HR SIZE=5 NOSHADE>
<H2> BE81 - Register terminology </H2>
<TABLE BORDER COLS=2 WIDTH="75%" >
<TR><TD>
Section: </TD><TD> all
</TD></TR><TR><TD>
Date Submitted: </TD><TD> 980914
</TD></TR><TR><TD>
Requestor: </TD><TD> Stuart Sutherland (stuart@sutherland.com)
</TD></TR><TR><TD>
Status: </TD><TD> Submitted
</TD></TR><TR><TD>
Analyzed by: </TD><TD> TBD
</TD></TR>
</TABLE>
<H3> Details </H3>
There is a discrepancy in terminology between the HDL sections and the PLI
sections of the LRM, which the PLI task force feels would be best corrected
in the HDL portion.
The HDL lumps the keywords reg, integer, time and real into the "register"
data type class. I'm sure we have all dealt with the confusion the term
"register" causes when hardware designers try to learn Verilog--I won't
belabor the issue.
In the PLI, the VPI part of the standard documents all Verilog objects and
their relationships with other objects. The VPI does not use the term
"register". It treats "reg" as a unique object type, and then has a class
of objects called "variables" which includes integer, time and real (pages
537 and 538 of the 1364-1995 LRM)
Please consider making the same distinction in the HDL sections of the LRM
that are already in the PLI sections. Section 3 almost makes the
distinction already. Section 3.2.2 (using the 1364-1995 numbering) deals
solely with the reg data type, and section 3.9 deals with the integer, time
and real types. It should be a relatively minor change to Section 3 to
eliminate the term "register" as a data type, and to distinguish between
"reg" and "variables". A global search of the remaining sections of the
LRM would simply replace "register" with the appropriate "reg", "variable"
or "reg or variable" terms.
A note could be added to section 3 explaining that in previous versions of
the Verilog standard, the term "register" was used to encompass both the
reg and variable types, but that the term is no longer used as a Verilog
data type because Stu Sutherland got tired of explaining to new Verilog
users that a data type register did not imply a hardware register (or words
to that effect) ;)
Please discuss this suggestion as soon as possible and let us know your
thoughts. The PTF is currently working on adding multi-dimensional arrays
to the VPI diagrams, and we would like to use consistent terminology as the
HDL sections of the standard.
Thanks,
Stu
<PRE>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Stuart Sutherland Sutherland HDL Inc.
stuart@sutherland.com 22805 SW 92nd Place
phone: 503-692-0898 Tualatin, OR 97062
www.sutherland.com
Specializing in Verilog HDL consulting and training.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
</PRE>
<HR SIZE=5 NOSHADE>
</BODY>
</HTML>
</x-html><x-html><HTML>
<HEAD>
<TITLE> BE82 </TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF">
<BR>
<HR SIZE=5 NOSHADE>
<H2> BE82 - zero size in sized number </H2>
<TABLE BORDER COLS=2 WIDTH="75%" >
<TR><TD>
Section: </TD><TD> 2.5.1 and A.8
</TD></TR><TR><TD>
Date Submitted: </TD><TD> 981023
</TD></TR><TR><TD>
Requestor: </TD><TD> Jay Bhasker (jbhasker@lucent.com)
</TD></TR><TR><TD>
Status: </TD><TD> Proposal
</TD></TR><TR><TD>
Analyzed by: </TD><TD> Anders Nordstrom
</TD></TR>
</TABLE>
<H3> Details </H3>
I am not sure what is the suggested way to file a bug report.
Thus, I am sending it to you, as you are the task leader of the BTF.
1364-1995 does not define the the semantics of size in a sized number when it
is 0.
0'b101, for example.
LRM says that size must be an unsigned decimal number. What if it is zero?
I think it needs to be reworded to "size must be an unsigned non-zero
decimal number".
- bhasker, jbhasker@lucent.com
<H3> Proposal </H3>
The size of a sized number must be non zero for the number
to be meaningful.
Change the second sentence in the first paragraph on page 7 to: <BR>
"It shall be specified as a non-zero unsigned decimal number."
In Syntax 2-1 on page 6 and Section A.8 on page 602: <BR>
Replace "size" in the syntax for decimal, binary, octal and hex
number with "non_zero_size".
Add the following syntax:
<PRE>
non_zero_size ::=
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
</PRE>
<HR SIZE=5 NOSHADE>
</BODY>
</HTML>
</x-html>From ???@??? Mon Nov 30 09:44:38 1998
Return-Path: <owner-btf@boyd.com>
Received: (from majordomo@localhost)
by gw.boyd.com (8.8.7/8.8.5) id JAA19178
for btf-list; Mon, 30 Nov 1998 09:40:07 -0800
X-Authentication-Warning: gw.boyd.com: majordomo set sender to owner-btf@boyd.com using -f
Received: from smtpott1.nortel.ca (smtpott1.nortel.ca [192.58.194.78])
by gw.boyd.com (8.8.7/8.8.5) with ESMTP id JAA19175
for <btf@boyd.com>; Mon, 30 Nov 1998 09:39:53 -0800
Received: from zcard00n.ca.nortel.com by smtpott1;
Mon, 30 Nov 1998 12:36:05 -0500
Received: from zmerd004.ca.nortel.com by zcard00n.ca.nortel.com
with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8)
id XTT35Z2N; Mon, 30 Nov 1998 12:35:08 -0500
Received: from wmers00q.ca.nortel.com by zmerd004.bnr.ca
with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8)
id XN85BA1V; Mon, 30 Nov 1998 12:35:08 -0500
Message-ID: <3662D74C.E3058DD3@americasm01.nt.com>
Date: Mon, 30 Nov 1998 12:35:08 -0500
From: "Anders Nordstrom" <Anders.Nordstrom.andersn@nt.com>
Reply-To: "Anders Nordstrom" <Anders.Nordstrom.andersn@nt.com>
Organization: Nortel Networks
X-Mailer: Mozilla 4.06 [en] (X11; I; SunOS 5.6 sun4m)
MIME-Version: 1.0
To: btf reflector <btf@boyd.com>
Subject: REMINDER New BTF Conference Calls
Sender: owner-btf@boyd.com
Precedence: bulk
Status: RO
<x-html><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000FF" VLINK="#FF0000" ALINK="#000088">
Team,
It is today!
Regards,
Anders
<PRE>--
+-------------------------------------------------------------------------+
| Anders Nordstrom |
| Senior ASIC Designer |
| |
| Nortel Networks Email: andersn@nortelnetworks.com |
| P.O. Box 3511 Station C Phone: 613-763-9186 |
| Ottawa, Ontario K1Y 4H7 Fax: 613-763-2626 |
+-------------------------------------------------------------------------+</PRE>
</BODY>
</HTML>
</x-html>Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-Disposition: inline
Date: Mon, 30 Nov 1998 17:36:32 +0000
Message-ID: <3652FD9F.5E030E66@americasm01.nt.com>
Date: Wed, 18 Nov 1998 12:02:23 -0500
From: "Anders Nordstrom" <Anders.Nordstrom.andersn@nt.com>
Reply-To: "Anders Nordstrom" <Anders.Nordstrom.andersn@nt.com>
Organization: Nortel Networks
X-Mailer: Mozilla 4.06 [en] (X11; I; SunOS 5.6 sun4m)
MIME-Version: 1.0
To: btf reflector <"btf@boyd.com Jskud"@Jskud.com>
Subject: New BTF Conference Calls
<x-html><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000FF" VLINK="#FF0000" ALINK="#000088">
Dear BTF Members,
I have set up three more weekly BTF conference calls so that we can
close more of the
<BR>remaining open errata and enhancements.
<BR>Note that January 11, 1999 is the deadline for submitting proposals
to the 1364 WG for
<BR>inclusion in Draft 2 of the LRM.
<BR>
Date: Mondays November 23, 30 and December 7, 1998
<BR>Time: 1 - 3 pm EST or 10 am - 12 pm PST
<BR>Phone: 1-613-763-6338
<BR>passcode: 605451#
<BR>
Regards,
Anders
<BR>
<PRE>--
+-------------------------------------------------------------------------+
| Anders Nordstrom |
| Senior ASIC Designer |
| |
| Nortel Networks Email: andersn@nortelnetworks.com |
| P.O. Box 3511 Station C Phone: 613-763-9186 |
| Ottawa, Ontario K1Y 4H7 Fax: 613-763-2626 |
+-------------------------------------------------------------------------+</PRE>
</BODY>
</HTML>
</x-html>From ???@??? Tue Dec 01 14:03:34 1998
Return-Path: <owner-btf@boyd.com>
Received: (from majordomo@localhost)
by gw.boyd.com (8.8.7/8.8.5) id NAA02044
for btf-list; Tue, 1 Dec 1998 13:57:41 -0800
X-Authentication-Warning: gw.boyd.com: majordomo set sender to owner-btf@boyd.com using -f
Received: from mailgate.nortel.ca (mailgate.nortel.ca [192.58.194.74])
by gw.boyd.com (8.8.7/8.8.5) with ESMTP id NAA02041
for <btf@boyd.com>; Tue, 1 Dec 1998 13:57:27 -0800
Received: from zcard00n.ca.nortel.com by mailgate;
Tue, 1 Dec 1998 16:56:51 -0500
Received: from zmerd004.ca.nortel.com by zcard00n.ca.nortel.com
with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8)
id XTT36P68; Tue, 1 Dec 1998 16:56:49 -0500
Received: from wmers00q.ca.nortel.com by zmerd004.bnr.ca
with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8)
id XN85BGA0; Tue, 1 Dec 1998 16:56:48 -0500
Message-ID: <36646622.64E3F5F1@americasm01.nt.com>
Date: Tue, 01 Dec 1998 16:56:50 -0500
From: "Anders Nordstrom" <Anders.Nordstrom.andersn@nt.com>
Reply-To: "Anders Nordstrom" <Anders.Nordstrom.andersn@nt.com>
Organization: Nortel Networks
X-Mailer: Mozilla 4.06 [en] (X11; I; SunOS 5.6 sun4m)
To: btf reflector <btf@boyd.com>
Subject: BTF Conf call Dec 7 Agenda
MIME-version: 1.0
Content-type: text/html; charset="us-ascii"
Content-transfer-encoding: 7bit
Sender: owner-btf@boyd.com
Precedence: bulk
Status: RO
<x-html><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000FF" VLINK="#FF0000" ALINK="#000088">
Dear BTF Members,
The next BTF conference call is scheduled for:
Date: Monday December 7, 1998
<BR>Time: 1 - 3 pm EST or 10 am - 12 pm PST
<BR>Phone: 1-613-763-6338
<BR>passcode: 605451#
<BR>
As you know the deadline for Draft 2 of the LRM is fast approaching.
We need to have all errata
<BR>and enhancements approved by the BTF by January 11 if they are to make
it into the LRM.
<BR>Everyting that is passed by the 1364 WG on the January 25 meeting will
be included in Draft 2.
At this point it is more important to close on LRM errata and older
enhancement requests than
<BR>to add significant new functionality to the language. Although we have
come a long way towards
<BR>a proposal for configurations, it will take more work before a widely
acceptable proposal can be
<BR>written and approved. This means that configurations will not make
it into the 1364-1999 standard.
<BR>I spoke with Maq Mannan about the status of Configurations and he wants
us to discuss
<BR>the issue on the December 14 conference call. Maq feels it is not a
critical part of the language
<BR>and that the schedule for releasing the LRM is more important.
At this comming Monday's conference call we will go thought all the
open errata and enhancements
<BR>and decide on where to go next with them.
<BR>Below is a list of all open enhancements and errata items. They may
also be found at www.ovi.org/ieee-1364/enhance.html
Open Enhancement Requests
<BR>-------------------
<BR>B5 - Configurations
<BR>B8 - Combinatorial Sensitivity List
<BR>B11 - Width extension beyond 32 bits
<BR>B13 - Indexed Parts selects
<BR>B25 - Add structures
<BR>B28 - Bottom testing loop
<BR>B29 - Line and File compiler directives
<BR>B31 - Specification of sized constants
<BR>B32 - Add non-blocking events
<BR>B33 - Parameter type declarations
<BR>B35 - PLA system task enhancements
Open LRM Errata
<BR>-----------
<BR>BE1 - Identifier errata
<BR>BE40 - Arrayed instances hierarchical references
<BR>BE49 - Missing task and function BNF
<BR>BE68 - Hierarchical and escaped identifiers
<BR>BE69 - Hierarchical system names
<BR>BE71 - Section 5.6.6 port connections
<BR>BE72 - Section 5.5 race conditions
<BR>BE79 - B19 negative number errata
<BR>BE81 - Register terminology
<BR>
Regards,
<BR>
Anders
<BR>
-- <BR>
+-------------------------------------------------------------------------+<BR>
| Anders Nordstrom
|<BR>
| Senior ASIC Designer
|<BR>
|
|<BR>
| Nortel Networks
Email: andersn@nortelnetworks.com |<BR>
| P.O. Box 3511 Station C
Phone: 613-763-9186
|<BR>
| Ottawa, Ontario K1Y 4H7
Fax: 613-763-2626
|<BR>
+-------------------------------------------------------------------------+
<BR>
</BODY>
</HTML>
</x-html>From ???@??? Fri Dec 04 19:30:33 1998
Return-Path: <owner-btf@boyd.com>
Received: (from majordomo@localhost)
by gw.boyd.com (8.8.7/8.8.5) id TAA02055;
Fri, 4 Dec 1998 19:28:43 -0800
Date: Fri, 4 Dec 1998 19:28:43 -0800
From: owner-btf@boyd.com
Message-Id: <199812050328.TAA02055@gw.boyd.com>
X-Authentication-Warning: gw.boyd.com: majordomo set sender to owner-btf@boyd.com using -f
To: owner-btf@boyd.com
Subject: BOUNCE btf@boyd.com: Admin request of type /\buns\w*b/i at line 3 Admin request of type /\buns\w*b/i at line 4 Admin request of type /\buns\w*b/i at line 7 Admin request of type /\buns\w*b/i at line 8
Status: RO
>From owner-btf Fri Dec 4 19:28:29 1998
Received: from hub1.san-jose.webnexus.net (hub1-20.san-jose.webnexus.net [209.140.224.20])
by gw.boyd.com (8.8.7/8.8.5) with ESMTP id TAA02048
for <btf@boyd.com>; Fri, 4 Dec 1998 19:28:26 -0800
Received: from mailgate.cadence.com (mailgate.Cadence.COM [158.140.2.1])
by hub1.san-jose.webnexus.net (8.9.1a/8.8.5/WN-1.3) with ESMTP id LAA13016
for <btf@boyd.com>; Thu, 3 Dec 1998 11:28:36 -0800 (PST)
Received: (from smap@localhost) by mailgate.cadence.com (8.8.5/8.6.8) id LAA27674 for <btf@boyd.com>; Thu, 3 Dec 1998 11:27:14 -0800 (PST)
Received: from rowlf.cadence.com(158.140.104.39) by mailgate.cadence.com via smap (mjr-v1.2)
id xma912713232.027664; Thu, 3 Dec 98 11:27:12 -0800
Received: from pc-tfitz.cadence.com (d15814010531 [158.140.105.31])
by rowlf.Cadence.COM (8.8.8/8.8.5) with SMTP id OAA21211
for <btf@boyd.com>; Thu, 3 Dec 1998 14:27:10 -0500 (EST)
Message-Id: <3.0.5.32.19981203142747.009d6700@rowlf.cadence.com>
X-Sender: tfitz@rowlf.cadence.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Thu, 03 Dec 1998 14:27:47 -0500
To: btf@boyd.com
From: Tom Fitzpatrick <tfitz@cadence.com>
Subject: Cleaning up section 2.5
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Syntax2-1
Decimal_number ::=
Unsigned_number
| decimal_base unsigned_number
real_number ::=
unsigned_number.unsigned_number
| unsigned_number[.unsigned_number] e|E [sign] unsigned_number
Section 2.5.1
Integer constants can be specified in decimal, hexadecimal, octal, or
binary format.
There are two forms to express integer constants. The first form is a
simple decimal number, which shall be specified as a sequence of digits 0
through 9. If the unary plus or minus operator is applied to the number, it
shall be treated as an expression (see Section 4.1.6). The second form
specifies a sized constant, which shall be composed of up to three tokens -
an optional size constant, a single quote followed by a base format
character, and the digits representing the value of the number.
4th paragraph p. 7
The single quote and the base format character(s) shall not be separated by
any white space.
6th paragraph p. 7
Simple decimal numbers without the size and the base format shall be
treated as signed integers, whereas the numbers specified with the base
format shall be treated as signed integers if the s designator is included
or as unsigned integers if the s designator is not included.
7th paragraph p. 7 (Replace)
A plus or a minus operator preceding the size constant is not part of the
number. Rather, it is an operator applied to the number, resulting in an
expression consisting of the operator and the number.
10th paragraph p. 7
If the digits representing the value of the number result in a smaller
number of bits than the specified size of the constant (8'hF, for example),
the value shall be padded to the left with zeros. If the leftmost bit in
the value is an x or a z, then an x or a z shall be used to pad to he left
respectively.
B19 Example p. 8
Change 4th example (replace incorrect backquote with single quote)
-4'sd15 // this is equivalent to -(-4'd1), or "0001".
Add new example
8'shf // The value 'f' requires 4 bits, which gets zero-extended to 8-bits,
// resulting in the value 15
Section 4.1.3 p. 30
The first paragraph of the Example section should read:
"This example shows four ways to writ ethe expression 'minus 12 divided by 3."
Change the 4th example to IntA = -4'sd12 / 3; // -4'sd12 is the negative
of the 4-bit
// quantity 1100, which is -4. -(-4) = 4.
// 4/3 = 1
Syntax2-1
Decimal_number ::=
Unsigned_number
| decimal_base unsigned_number
real_number ::=
unsigned_number.unsigned_number
| unsigned_number[.unsigned_number] e|E [sign] unsigned_number
Section 2.5.1
Integer constants can be specified in decimal, hexadecimal, octal, or
binary format.
There are two forms to express integer constants. The first form is a
simple decimal number, which shall be specified as a sequence of digits 0
through 9. If the unary plus or minus operator is applied to the number, it
shall be treated as an expression (see Section 4.1.6). The second form
specifies a sized constant, which shall be composed of up to three tokens -
an optional size constant, a single quote followed by a base format
character, and the digits representing the value of the number.
4th paragraph p. 7
The single quote and the base format character(s) shall not be separated by
any white space.
6th paragraph p. 7
Simple decimal numbers without the size and the base format shall be
treated as signed integers, whereas the numbers specified with the base
format shall be treated as signed integers if the s designator is included
or as unsigned integers if the s designator is not included.
7th paragraph p. 7 (Replace)
A plus or a minus operator preceding the size constant is not part of the
number. Rather, it is an operator applied to the number, resulting in an
expression consisting of the operator and the number.
10th paragraph p. 7
If the digits representing the value of the number result in a smaller
number of bits than the specified size of the constant (8'hF, for example),
the value shall be padded to the left with zeros. If the leftmost bit in
the value is an x or a z, then an x or a z shall be used to pad to he left
respectively.
B19 Example p. 8
Change 4th example (replace incorrect backquote with single quote)
-4'sd15 // this is equivalent to -(-4'd1), or "0001".
Add new example
8'shf // The value 'f' requires 4 bits, which gets zero-extended to 8-bits,
// resulting in the value 15
Section 4.1.3 p. 30
The first paragraph of the Example section should read:
"This example shows four ways to writ ethe expression 'minus 12 divided by 3."
Change the 4th example to IntA = -4'sd12 / 3; // -4'sd12 is the negative
of the 4-bit
// quantity 1100, which is -4. -(-4) = 4.
// 4/3 = 1
---------------
Tom Fitzpatrick
Senior Technical Marketing Manager Cadence Design Systems, Inc.
Cycle Simulation Products 270 Billerica Rd.
Logic Design and Verification Business Unit Chelmsford, MA 01824
x6438 (978)446-6438
This archive was generated by hypermail 2.1.4
: Mon Jul 08 2002 - 12:53:02 PDT
and
sponsored by Boyd Technology, Inc.