Objet : Developers list for StarPU
Archives de la liste
- From: Samuel Thibault <samuel.thibault@ens-lyon.org>
- To: Cyril Roelandt <cyril.roelandt@inria.fr>
- Cc: starpu-devel@lists.gforge.inria.fr
- Subject: Re: [Starpu-devel] Seek and destroy memory leaks.
- Date: Wed, 1 Feb 2012 08:56:57 +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>
Cyril Roelandt, le Wed 01 Feb 2012 02:50:00 +0100, a écrit :
> On 02/01/2012 02:36 AM, Samuel Thibault wrote:
> >Cyril Roelandt, le Wed 01 Feb 2012 02:24:55 +0100, a écrit :
> >>I am afraid that every test will return EXIT_FAILURE, since the result
> >>will
> >>not be good, but is that really a problem ?
> >
> >I don't think it's a problem, we just need to pass -k to make so it
> >still runs them all.
>
> Is that a valgrind option ? I can't find it in the manpage.
EPARSE: "to pass -k to 'make' so it still runs them all" :)
Samuel
- [Starpu-devel] Seek and destroy memory leaks., Cyril Roelandt, 01/02/2012
- <Suite(s) possible(s)>
- Re: [Starpu-devel] Seek and destroy memory leaks., Samuel Thibault, 01/02/2012
- Re: [Starpu-devel] Seek and destroy memory leaks., Cyril Roelandt, 01/02/2012
- Re: [Starpu-devel] Seek and destroy memory leaks., Nathalie Furmento, 01/02/2012
- Message indisponible
- Re: [Starpu-devel] Seek and destroy memory leaks., Samuel Thibault, 01/02/2012
- Re: [Starpu-devel] Seek and destroy memory leaks., Cyril Roelandt, 01/02/2012
Archives gérées par MHonArc 2.6.19+.