[Pkg-opencl-devel] can opencl-icds built against llvm 3.4 (beignet 0.8) and llvm 3.5 (mesa/libclc) coexist in a process?

[Rebecca N. Palmer]

> llvm errors Giuseppe reported and that depend on the icd loading order?
In sid (platform order mesa,beignet,pocl), I get those errors on trying 
to use either pocl or beignet 0.9.3, but _not_ beignet 0.8, with 
mesa-opencl-icd installed.  #768185 was also beignet 0.9.3.

In testing (platform order beignet,pocl,mesa, with mesa-opencl-icd 
depending on both llvm 3.5 (directly) and 3.4 (via libclc)), I get a 
different error (that looks like it comes from beignet) with beignet 
0.9.3, but not pocl or beignet 0.8.

I agree that this is a bug, but don't know yet where it is.

Using pocl and either version of beignet at the same time works; I don't 
have the hardware to actually use mesa-opencl-icd.

(When testing this, remember that up/downgrading beignet may not take 
effect without a reboot, #769293.)

> ... does pocl use llvm, too?
Yes, 3.5, dynamically linked by default.  This has been known to cause 
version mismatch issues when used together with mesa (llvmpipe libGL, 
not mesa-opencl-icd): https://github.com/pocl/pocl/issues/46  They 
suggest linking statically, which is done by passing 
--enable-static-llvm to the configure step, 
https://lists.debian.org/debian-mentors/2014/04/msg00283.html

beignet (both versions) already links llvm statically and disables cl-gl 
sharing (because it was broken by mesa changes), but I haven't actually 
tried using it with mesa llvmpipe.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: two_icd_test.py
Type: text/x-python
Size: 1070 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-opencl-devel/attachments/20141112/d7294f9b/attachment.py>