[Libclc-dev] Beignet wants to apply libclc

Tom Stellard tom at stellard.net
Tue Sep 16 07:33:35 PDT 2014

On Tue, Sep 16, 2014 at 09:26:27PM +0800, He Junyan wrote:
> hi,
> I am a developer of Intel's open source CL stack, which name is Beignet.
> We used to include all the CL built-ins in one huge header file and
> compile it as a PCH.
> We find some disadvantages of that manner and switched to the same
> manner as libclc recently. We now have a internal lib, which play the
> same role as the libclc, and we are attempting to apply the libclc to
> replace it in the near future.
> But I find some problems when I try to integrate the libclc:
> 1. There is no support for Image related functions in it now. Is that on
> your plan?

libclc only supports GPU targets and these targets require target-specific
implementations of the image functions, which is why there are no
generic image functions.  If you were to use libclc for Intel GPUs, you
would need to implement your own target specific image functions.

> 2. I find it is not compatible with OpenCL1.2, which Beignet must
> support, are you going to implement it?

In what way is it not compatible?  The goal is to implement everything,
but as far as I know no one has spent much time on OpenCL 1.2 features.

> 3. Because beignet as a backend does not completely follow the PTX or
> NVPTX framework, it has a lot of internal implementations for the
> builtin functions. We may need to add a lot of files for it, is that
> acceptable?

Yes, if you are adding a new target with a lot of target specific
implementations, then it is not a problem if there are a lot of files.


> Thanks
> _______________________________________________
> Libclc-dev mailing list
> Libclc-dev at pcc.me.uk
> http://www.pcc.me.uk/cgi-bin/mailman/listinfo/libclc-dev

More information about the Libclc-dev mailing list