Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] starpu_task_destroy

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] starpu_task_destroy


Chronologique Discussions 
  • From: Samuel Thibault <samuel.thibault@ens-lyon.org>
  • To: Usman Dastgeer <usman.dastgeer@liu.se>
  • Cc: "starpu-devel@lists.gforge.inria.fr" <starpu-devel@lists.gforge.inria.fr>
  • Subject: Re: [Starpu-devel] starpu_task_destroy
  • Date: Tue, 14 Feb 2012 11:49:28 +0100
  • List-archive: <http://lists.gforge.inria.fr/pipermail/starpu-devel>
  • List-id: "Developers list. For discussion of new features, code changes, etc." <starpu-devel.lists.gforge.inria.fr>

Usman Dastgeer, le Tue 14 Feb 2012 11:43:27 +0100, a écrit :
> Then, just skimming through doc at starpu_task_destroy description I got bit
> confused:

> — Function: void starpu_task_destroy (struct starpu_task *task)
>
>
> Free the resource allocated during starpu_task_create and associated
> with task. This function can be called automatically after the
> execution of
> a task by setting the destroy flag of the starpu_task structure (default
> behaviour). Calling this function on a statically allocated task
> results in
> an undefined behaviour.

Ok, so that's the place which is not clear.

> and default value of destroy field says "0"

I've just fixed it.

Samuel





Archives gérées par MHonArc 2.6.19+.

Haut de le page