Hi Martin and Michal:

On 15.03.2017 08:25, Michal Babej wrote:
> Basically, instead of 2 compilers now (system and opencl kernel
> compiler) you would have to deal with 3 compilers. E.g. if you want
> to compile for ARM on x86-64, you'll need:
>
> 1) arm-whatever-gcc 2) llvm x86-64 (for compiling pocl's kernel
> library code on x86-64) 3) llvm arm
>
> The new compiler (3) is required because pocl has some code that
> links against LLVM, and you need to link it to target arch LLVM. It's
> not

Do you mean LLVMFileUtils.cc? I think those functions should be
rather easy to convert to something with less deps. Do you Michal know
something else that uses Clang/LLVM for something not related to
kernel compilation?

> impossible to get done, just quite a bit of work. I've originally
> started cross-compilation work with this goal, but dropped it since
> non-LLVM builds were sufficient for us. Plus you'll need all the
> libraries (hwloc etc) for target, and pkg-config must recognize them
> and their versions.

hwloc is not required (at least was not in the autotools scripts),
it should fallback to a non-hwloc build which just doesn't support
so many of the device queries (at the moment).

Also it might be interesting to now try to replace 1) with Clang/LLVM.
It might be easier to cross-compile using Clang than with gcc due to
LLVM's multi-backend architecture and with lld getting stabler.

BR,
-- 
Pekka

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
pocl-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pocl-devel

Reply via email to