Re: [sv-ec] FW: [sv-bc] Can a function contain a fork/join/any/none?

From: Steven Sharp <sharp_at_.....>
Date: Mon Dec 04 2006 - 14:48:24 PST
>From: "Bresticker, Shalom" <shalom.bresticker@intel.com>

>2. 1364-2005 says in 10.2.3, regarding tasks:
>
>"Because variables declared in automatic tasks are deallocated at the
>end of the task invocation, they shall not be used in certain constructs
>that might refer to them after that point:
>
>- They shall not be assigned values using nonblocking assignments or
>procedural continuous assignments.
>
>- They shall not be referenced by procedural continuous assignments or
>procedural force statements.
>
>- They shall not be referenced in intra-assignment event controls of
>nonblocking assignments.
>
>- They shall not be traced with system tasks such as $monitor and
>$dumpvars."
>
>and 10.3 says,
>
>"The results of the following activities that can be initiated by a task
>are not specified if the task is disabled:
>- Results of output and inout arguments
>- Scheduled, but not executed, nonblocking assignments
>- Procedural continuous assignments (assign and force statements)"
>
>Should the proposal change any of this, at least regarding the
>nonblocking and procedural continuous assignments?
>
>
>3. If not, the proposal might need to include similar statements
>regarding functions.


Unlike a task, a function cannot be disabled.  So I don't think
there is an issue with disables.  But the restrictions you listed
for variables in automatic tasks should definitely be extended to
all automatic variables.


Steven Sharp
sharp@cadence.com
Received on Mon Dec 4 14:48:33 2006

This archive was generated by hypermail 2.1.8 : Mon Dec 04 2006 - 14:48:42 PST