Subject: Re: [sv-bc] Fwd: Re: [sv-cc] Semantics of disable as applied to task/func arguments
From: Dave Rich (David.Rich@synopsys.com)
Date: Fri Oct 24 2003 - 11:38:24 PDT
Folks in the SV-CC
I believe these are all non-issues because
A) you are not allowed to disable a function, only tasks and named blocks
B) there is no required action for ref arguments upon exiting a task. I
would expect deterministic results if I modify a variable by reference,
then later disable the task.
C) The behavior of dynamic objects specified by the lifetime in the
scope where they are declared. Static variables are not effected by
exiting the scope. Automatic variable disappear when exiting the scope.
I should not matter how the scope gets exited, e.g. by a disable, or by
an implicit or explicit return.
Dave
Karen Pieper wrote:
>
>>
>> From: Swapnajit Mittra <mittra@juno.com>
>>
>>
>> Hello Johnny and Karen,
>>
>> The following issue came up in sv-cc that we feel should
>> be looked into by sv-bc. Please let us know if you have
>> any other question. The following email can also be found
>> from sv-cc email archive:
>>
>> http://www.eda.org/sv-cc/hm/1528.html
>>
>> Regards,
>>
>> --
>> Swapnajit Mittra
>> Project VeriPage ::: http://www.angelfire.com/ca/verilog
>>
>> -- "Joao Geada" <Joao.Geada@synopsys.com> wrote:
>> Hi all,
>>
>> Just to document the issue that came up during today's sv-cc meeting:
>>
>> what is the behavior of task/function output/inout/ref arguments when
>> that
>> invocation of the task or function is disabled ?
>>
>> In IEEE 1364-2001, Section 11 (page 162) it states that:
>>
>> "The results of the following activities that may be initiated by a task
>> are not specified if the task or function is disabled:
>> Results of output and inout arguments"
>>
>> I believe a (minor) errata is required to carry this rule forward
>> into SV 3.1, stating that the general principle applies.
>>
>> ie something like:
>> The results of the following activities that may be initiated by a
>> task +or function+
>> are not specified if the task or function is disabled:
>> Results of output, inout +and reference+ arguments
>>
>> (the + signs indicate additions to the text in the 1364-2001)
>>
>> Additionally, it would also be desirable to state what happens to items
>> allocated via "new" in task/function invocations that are disabled.
>>
>> Joao
>> ==============================================================================
>>
>> Joao Geada, PhD Principal Engineer Verif
>> Tech Group
>> Synopsys, Inc TEL: (508)
>> 263-8083
>> 377 Simarano Drive, Suite 300, FAX: (508)
>> 263-8069
>> Marlboro, MA 01752, USA
>> ==============================================================================
>>
>>
>> ________________________________________________________________
>> The best thing to hit the internet in years - Juno SpeedBand!
>> Surf the web up to FIVE TIMES FASTER!
>> Only $14.95/ month - visit www.juno.com to sign up today!
>
>
>
>
-- -- David.Rich@Synopsys.com Technical Marketing Consultant http://www.SystemVerilog.org tele: 650-584-4026 cell: 510-589-2625
This archive was generated by hypermail 2b28 : Fri Oct 24 2003 - 11:44:22 PDT