22.4.2015, 17:21, Tiago Gehring kirjoitti:
> Thanks Pekka. I think that I will not give up on my idea of a fully
> contained pocl library (i.e. all static LLVM and libclang) after all
> then (or at least leave it as an alternative). How difficult do you
> think would it be to replace the clang binary calls by library ones?

I haven't checked what type of APIs are available for the binary
linking, maybe Kalle has the best idea?

> 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.

_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.

-- 
Pekka

------------------------------------------------------------------------------
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

Reply via email to