Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] setting the clBuildProgram() option parameter

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] setting the clBuildProgram() option parameter


Chronologique Discussions 
  • From: Cédric Augonnet <cedric.augonnet@inria.fr>
  • To: Jonathan Adamczewski <jadamcze@utas.edu.au>
  • Cc: starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] setting the clBuildProgram() option parameter
  • Date: Mon, 04 Apr 2011 19:01:21 +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/04/2011 17:39, Jonathan Adamczewski wrote:
clBuildProgram() is called within starpu_opencl_load_opencl_from_string() with a hard-coded options parameter of "-Werror -cl-mad-enable". I would like to be able to set different options, such as include paths and macro definitions for the opencl kernels I am using with starpu.

If I were to add support for different option strings, what would be an appropriate/preferred way to do so? Options I can see are:
- extra parameter passed to the function (which needs to be added to other functions, too)
- extra const char* field in struct starpu_opencl_program (one option for all opencl programs)
- array of const char* fields in struct starpu_opencl_program, one for each program
- environment variable

Thanks

Jonathan.

Hi Jonathan,

Thanks again for your valuable feedback! Would not an extra "const char *" parameter to both starpu_opencl_load_opencl_from_file and starpu_opencl_load_opencl_from_string be sufficient ? This seems to be the most natural and also the cleanest solution.

Best,
Cédric





Archives gérées par MHonArc 2.6.19+.

Haut de le page