[sv-cc] [Fwd: RE: SV-CC meeting tomorrow]

-------- Original Message --------
Subject: RE: SV-CC meeting tomorrow
Date: Tue, 30 Nov 2004 16:46:48 -0800
From: "Brad Pierce" <Brad.Pierce@synopsys.com>
Reply-To: <Brad.Pierce@synopsys.com>
To: <chas>

Hi, thanks for letting me know. The good news is that today the SV-BC
passed proposals for these issues, so the SV-CC can probably skip these.

The proposal for 51 said that integers are not packed arrays.

    "Although an integer type with a predefined width n is not a packed
array, it matches (see Section 5.8.1), and can be selected from as if it
were, a packed array type with a single [n-1:0] dimension."

  The proposal for 41/169 said that names are not required in a prototype
unless argument binding by name or default values are used (or additional
unpacked arrays are declared). The BNF was corrected to make these names
optional. The text in 19.6 now says (see especially the second paragraph)--

   "A function prototype specifies the types and directions of the arguments
and the return value of a function which is defined elsewhere. Similarly, a
task prototype specifies the types and directions of the arguments of a task
which is defined elsewhere. In a modport, the import and export constructs
can either use function or task prototypes or use just the identifiers. The
only exceptions are when a modport is used to import a function or task from
another module and when default argument values or argument binding by name
are used, in which cases a full prototype shall be used.

   "The number and types of arguments in a prototype must match the argument
types in the function or task declaration. The rules for type matching are
described in Section 5.8.1, Matching Types. If a default argument value is
needed in a subroutine call, it shall be specified in the prototype. If an
argument has default values specified in both the prototype and the
declaration, the specified values need not be the same, but the default
value used shall be the one specified in the prototype. Formal argument
names in a prototype shall be optional unless default argument values or
argument binding by name are used or additional unpacked dimensions are
declared. The formal argument names in the prototype shall be the same as
the formal argument names in a declaration."

-- Brad

-----Original Message-----
From: Charles Dawson [mailto:chas@cadence.com]
Sent: Tuesday, November 30, 2004 4:23 PM
To: Brad Pierce
Subject: SV-CC meeting tomorrow

Hi Brad,

We have our last SV-CC meeting tomorrow prior to our 12/1 deadline for
addressing
issues. It was requested by Bassam that Items 41, 51, and 169 be discussed
at
the SV-CC meeting and that you attend the discussion. If it is at all
possible,
please join us. I will send out an agenda with the time and dial-in info
later
tonight, but I believe it is at 8:30am your time.

    -Chas

--
Charles Dawson
Senior Engineering Manager
NC-Verilog Team
Cadence Design Systems, Inc.
270 Billerica Road
Chelmsford, MA  01824
(978) 262 - 6273
chas@cadence.com
-- 
Charles Dawson
Senior Engineering Manager
NC-Verilog Team
Cadence Design Systems, Inc.
270 Billerica Road
Chelmsford, MA  01824
(978) 262 - 6273
chas@cadence.com