I agree with Steve. It's also not generally feasible to determine statically whether a conditionally blocking task is a simple zero-delay task or not. And, in the case of static tasks, this also opens up the issue of when should the arguments be copied into the task. Arturo ----- Original Message ----- From: "Steven Sharp" <sharp@cadence.com> To: <sv-ec@eda.org>; <gordonv@Model.com> Sent: Thursday, April 28, 2005 3:32 PM Subject: Re: [sv-ec] Scheduling cycle Gord wrote: > 2) a call to a non-program function or task should delay > the thread to the Reactive NBA region before AND after > the enable But this means that a call to a 'pure' function or simple zero-delay task defined in a package would result in blocking the thread. This is probably not what was intended when the subroutine was written to have no delays. Steven Sharp sharp@cadence.comReceived on Thu Apr 28 16:42:25 2005
This archive was generated by hypermail 2.1.8 : Thu Apr 28 2005 - 16:43:31 PDT