Objet : Developers list for StarPU
Archives de la liste
- From: Samuel Thibault <samuel.thibault@ens-lyon.org>
- To: Jeffrey Dimarco <jdimarco@udel.edu>
- Cc: starpu-devel@lists.gforge.inria.fr
- Subject: Re: [Starpu-devel] About tracing a StarPU application
- Date: Wed, 15 May 2013 09:40:54 +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>
Jeffrey Dimarco, le Wed 15 May 2013 08:38:16 +0200, a écrit :
> I noticed that the trace produced by StarPU uses the "FxT" tool, which
> produces
> a binary trace file. Is there any way that I could produce an ASCII trace
> file
> instead? I know that the .paje format is available as well, but I was
> hoping
> to analyze the trace in a general format beforehand.
Yes, I happen to have added a mention in the documentation just
yesterday :)
You can use
fxt_print -o -f the_file
Samuel
- [Starpu-devel] About tracing a StarPU application, Jeffrey Dimarco, 10/05/2013
- Re: [Starpu-devel] About tracing a StarPU application, Samuel Thibault, 15/05/2013
Archives gérées par MHonArc 2.6.19+.