RE: [sv-cc] Re: questions on SV-CC 303/PTF 342 (fwd)

All,

I think this phrasing of "tags" indicating optional arguments is obsolete.
It applied to several ACC routines where the number of arguments were
affected by acc_configure(). Since those routines have all been deprecated,
the statement about them should also be deprecated.

However, there is at least one VPI routine I know of off the top of my head
that does have a variable number of arguments, vpi_control(). Therefore, it
would be appropriate to leave in the first sentence of the paragraph in
question, and delete the remainder of the paragraph.

This type of change is appropriate for the changes that can be made between
the pre-ballot review draft, which is to review the changes made to the
standard, and the final ballot draft. The change is simply clarifying an
already approved change.

This should be opened as a new item and voted on by the SV-CC not later than
Feb 3. At that point, all changes planned for the ballot draft need to go
to the champions committee and then on to the P1800 for final approval.

Stu
~~~~~~~~~~~~~~~~~~~~~~~~~
Stuart Sutherland
stuart@sutherland-hdl.com
+1-503-692-0898
  

> -----Original Message-----
> From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On
> Behalf Of Shalom.Bresticker@freescale.com
> Sent: Sunday, January 16, 2005 7:21 AM
> To: sv-cc@eda.org
> Subject: [sv-cc] Re: questions on SV-CC 303/PTF 342 (fwd)
>
>
>
> --
> Shalom Bresticker Shalom.Bresticker
> @freescale.com
> Design & Verification Methodology Tel:
> +972 9 9522268
> Freescale Semiconductor Israel, Ltd. Fax:
> +972 9 9522890
> POB 2208, Herzlia 46120, ISRAEL Cell:
> +972 50 5441478
>
> [ ]Freescale Internal Use Only [ ]Freescale Confidential
> Proprietary
>
> ---------- Forwarded message ----------
> Date: Sun, 9 Jan 2005 14:47:56 +0200 (IST)
> From: Shalom.Bresticker@freescale.com
> To: Charles Dawson <chas@cadence.com>
> Subject: Re: questions on SV-CC 303/PTF 342
>
> Hi, Charles.
>
> Regarding the following text to be added to the beginning of
> Clause 27:
>
> "All arguments shall be considered mandatory unless
> specifically noted in the definition of the PLI routine. Two
> tags are used to indicate arguments that may not be required:
> Conditional: Arguments tagged as conditional shall be
> required only if a previous argument is set to a specific
> value, or if a call to another PLI routine has configured the
> PLI to require the arguments. The PLI routine definition
> explains when conditional arguments are required.
> Optional: Arguments tagged as optional may have default
> values within the PLI, but they may be required if a previous
> argument is set to a specific value, or if a call to another
> PLI routine has con-figured the PLI to require the arguments.
> The PLI routine definition explains the default values and
> when optional arguments are required."
>
> So far as I can see, these tags are not used at all in Clause 27.
>
> Please check.
>
> Thanks,
> Shalom
>
> --
> Shalom Bresticker Shalom.Bresticker
> @freescale.com
> Design & Verification Methodology Tel:
> +972 9 9522268
> Freescale Semiconductor Israel, Ltd. Fax:
> +972 9 9522890
> POB 2208, Herzlia 46120, ISRAEL Cell:
> +972 50 5441478
>
> [ ]Freescale Internal Use Only [ ]Freescale Confidential
> Proprietary
>
>
>
Received on Mon Jan 17 10:15:05 2005