Pekka
In principle, creating the kernel libraries etc. could also happen at
run time, so that no separate install step would be necessary. To
"install" pocl, one would then run it once, running e.g. a test
program.
Pocl may be installed on a heterogeneous cluster, i.e. a file system
where different workstations / compute nodes using the same file
system have different capabilities. Thus it may be necessary to
"install" pocl multiple times, with cumulative kernels, or to pass
multiple architectures to the install script. A typical use case would
be a user installing pocl into a shared home directory for a cluster
that has several generations of compute nodes.
In the latter case, one would also need to distinguish at run time on
what architecture one is running, presumably automatically, so that
optimal kernel code can be generated.
Alternatively, we could support different device types, one for each
CPU architecture. This may be more elegant than trying to insert a
distinction between different CPU architectures and keeping this
invisible to the user ("why does this binary kernel not work any
more?"). In fact, the longer I think about this the more I like this
idea -- making CPU architectures visible to the end user seems a good
idea.
-erik
On Sun, Oct 26, 2014 at 6:51 AM, Pekka Jääskeläinen
<[email protected]> wrote:
> Hi,
>
> As the old notes were lost due to Sourceforge wiping the old
> wiki, I rewrote the plan/thoughts for improving the performance/portability of
> pocl binary distributions here:
>
> https://github.com/pocl/pocl/wiki/Install-time-built-kernel-builtin-libraries
>
> Maybe I forgot something? Any comments welcomed.
>
> --
> --Pekka
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> pocl-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/pocl-devel
--
Erik Schnetter <[email protected]>
http://www.perimeterinstitute.ca/personal/eschnetter/
AIM: eschnett247, Skype: eschnett, Google Talk: [email protected]
------------------------------------------------------------------------------
_______________________________________________
pocl-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pocl-devel
