Le 18/10/2013 15:27, Pekka Jääskeläinen a écrit :
> One solution I proposed was to distribute and install the sources of
> the kernel lib and build the optimized kernel bitcode libs on-demand.
> Then these would be cached to the user's home dir, so only the first use
> would get the performance hit (there could be a separate population
> step in the installation of the binary that does it).
Some remarks:
1) it seems globally ok from my point of view
2) do not forget to look at system path (ie read-only) for precompiled
libs (as stated in your parenthesis, the lib compilation can be
done at install time by dpkg/yum/rpm/...)
3) allow multiple versions installed in parallel (directory with
version number ?)
Else, upgrading a machine with programs using pocl will require to
upgrade all programs (using pocl) at the same time
4) allow multiple target versions installed at the same time
(directory with precise target ?, file header that list all "feature"
of the libs (similar to *.h.gch gcc compiled headers) ?, ... )
HOME can be shared between different machines
Regards,
Vincent
--
Vincent Danjean GPG key ID 0x9D025E87 [email protected]
GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo: deb http://people.debian.org/~vdanjean/debian unstable main
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
pocl-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pocl-devel
