On Wed, Apr 22, 2015 at 8:11 PM, Pekka Jääskeläinen <[email protected]> wrote: > 22.4.2015, 17:21, Tiago Gehring kirjoitti: >> And regarding the other question (about the compilation of the *.bc >> files) I agree with you that in the long run the rebuilding of the >> kernel bitcode (or getting rid of it altogether) is a good idea. Are any >> LLVM (or other) external headers >> required to compile the kernel bitcode? > > Yes, at least the _kernel.h (which contains the declarations etc. for > the builtins) which includes some pocl internal headers. Check what > make does in lib/kernel/host for a starting point for the bitcode > builder.
I was expecting _kernel.h to be always a dependency, my question was actually if LLVM headers have to always be lying around (but I believe now that this is not the case). But thanks, I will check what the build process does as you suggested to look for any other dependencies (perhaps the pocl internal headers as you mentioned). > _kernel.h is needed also when building user kernels, so if you want to > bundle them also so there's nothing but libpocl.so and no data files, > they could be converted to a C string, linked in to libpocl.so, and > fed into Clang's preprocessing in the kernel compilation. Or something > better. This sounds like a good idea, if _kernel.h is used only internally to compile the kernels I guess it would make sense to just embed it in the code. Regarding the libclang dependencies, from what Kalle wrote I guess that the main issue for having a complete self-contained pocl static lib is the linking step. Both lld and jit seems promising, if I have time I would be happy to give it a shot and try to contribute something to use one of both to remove the binary dependencies; but let's see if I can get to it first. The first thing that I would like to actually do is make _kernel.h and the *.bc files relocatable/support relative paths (or embeddable); this would already save me quite some trouble as I don't want to enforce a fixed location for the files (which would have to be installed system wide) nor have every user compile the code himself (especially in the case of Windows). ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
