Re: [Starpu-devel] starpu_codelet must be global?

[Nathalie Furmento <nathalie.furmento@labri.fr>]

The correct way is to use the function

starpu_codelet_init(struct starpu_codelet *cl);

to properly initialise a codelet. All examples provided with StarPU might not 
be doing it though. I just updated the documentation to clarify this issue.

Cheers,

Nathalie

On Apr 30, 15:59, Miguel Palhas wrote:
> I'm trying to mess around with the initial examples of starpu, and came
> across a strange error
>
> The original sample declares a global variable, struct starpu_codelet cl. I
> tried to make this variable local to the main function, basically doing
> this:
>
> // this is the old variable, commented out
> // struct starpu_codelet cl;
>
> int main() {
>   ...
>   // and this is the new one
>   struct starpu_codelet cl;
>   cl.where = STARPU_CPU
>   cl.cpu_funcs[0] = cpu_func;
>   cl.cpu_funcs[1] = NULL;
>   cl.nbuffers = 0;
>
>
> This version crashes with the following error:
> [1]    26482 illegal hardware instruction  ./a.out
>
> but if i just switch the comments and use the global variable instead, it
> all goes well again.
> I'm actually fine with this requirement, i just wanted to know if this is
> to be expected, and why?
>
> --
> Best Regards
> Miguel Palhas

> _______________________________________________
> Starpu-devel mailing list
> Starpu-devel@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/starpu-devel


--
----------------------------------------------------------------------------
Dr Nathalie Furmento                         CNRS R&D Engineer
Centre de Recherche INRIA Bordeaux Sud-Ouest http://www.labri.fr/~furmento/
200 avenue de la vieille Tour                Tel: +33 (0)5 24 57 41 20
33405 Talence cedex, FRANCE                  Fax: +33 (0)5 24 57 40 41
----------------------------------------------------------------------------