Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] Make the FxT-related code portable.

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] Make the FxT-related code portable.


Chronologique Discussions 
  • From: Cyril Roelandt <cyril.roelandt@inria.fr>
  • To: Samuel Thibault <samuel.thibault@ens-lyon.org>, starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] Make the FxT-related code portable.
  • Date: Wed, 25 Apr 2012 16:33:18 +0200
  • 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>

On 04/24/2012 06:13 PM, Samuel Thibault wrote:
Cyril Roelandt, le Tue 24 Apr 2012 14:23:27 +0200, a écrit :
On what systems have we tested StarPU with FxT ?

Just linux.

The attached patch should fix the build on FreeBSD.

As a default cases, we should probably just use pthread_self().

The thing is, I'm not sure it __really__ works on Darwin:
it is weird that they have a gettid syscall (cf.
http://elliotth.blogspot.fr/2012/04/gettid-on-mac-os.html).

It is completely unrelated with what we want, indeed. We could probably
just use pthread_self() there too.


Ok, I think I'll use OS-specific code for systems I can easily run tests on, and just call pthread_self() for all other systems. Btw, why don't we just use pthread_self everywhere ?

Cyril.





Archives gérées par MHonArc 2.6.19+.

Haut de le page