Den Tue, 29 Oct 2013 13:33:16 +0200 skrev Re: [pocl-devel] builtin libs autobuild:
> 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. > " We need pocl runtime building of the bitcode libraries per target variation (as required) and caching them for later use. " Do we? Need a cache I mean. What consumes time now is the indexing of the kernel library. I ran a profile of example1. Compiling the kernel source takes about 10% of the total execution time, parsing the kernel library takes 50%. Now, the example1 is a rather trivial kernel. The AESEncryptDecrypt is much more complex-looking, yet compiling it is less than 10% slower than the example1 kernel. This suggests that most of the compilation time is constant overhead. Which means, that the overhead of compiling the kernel runtime & on-demand from source would add only a moderate overhead, if we can selectively compile only the needed source files. The upside of this would of course be the elimination of version-platform-phasesofthemoon-dependant kernel cache. I would like to make more thorough measurements before committing to this approach, though... kalle ------------------------------------------------------------------------------ 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
