Hi all, I sketched some notes on how to improve the OpenCL C built-in bitcode library situation:
https://sourceforge.net/apps/mediawiki/pocl/index.php?title=Bitcode_libraries Any comments welcome. You can also edit the wiki directly. On 10/18/2013 04:56 PM, Vincent Danjean wrote: > 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 > -- Pekka ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
