Hi, Right, clLinkProgram() is unimplemented.
The first implementation might simply use LLVM bitcode linking and support only the bitcode "binary format", and thus assume the LLVM bitcode is always available. The 2nd version might link the final binaries in case LLVM IR is not available. If you decide to contribute to pocl development, support will be provided here and in #pocl. BR, Pekka On 30.05.2016 07:48, Marmaduke Woodman wrote: > hi > > I've built v0.13 against LLVM 3.7.1 with --enable-direct-linkage, but I > run into a run time link error, failing to find symbol clLinkProgram. > Indeed, the libOpenCL.so built by PoCL exports symbols for many CL API > functions but not this one. I just want to confirm: this part of the > unimplemented API in OpenCL? > > Am I better off trying to change the client program or contributing an > clLinkProgram implementation to PoCL (I've no idea what this entails)? > > Cheers, > Marmaduke -- Pekka ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
