[Libclc-dev] Beignet wants to apply libclc

He Junyan junyan.he at inbox.com
Wed Sep 17 00:22:19 PDT 2014


The beignet is a OpenCL driver only for Intel's GEN GPU.
According to this, I am sorry that we have to remove the pocl
from our candidate list.


On 二, 2014-09-16 at 11:03 -0400, Erik Schnetter wrote:
> On Tue, Sep 16, 2014 at 10:37 AM, Tom Stellard <tom at stellard.net> wrote:
> > On Tue, Sep 16, 2014 at 10:01:29AM -0400, Erik Schnetter wrote:
> >> He Junyan
> >>
> >> The pocl project <http://pocl.sourceforge.net/> also contains an
> >> implementation of the OpenCL run-time library, and I was similarly
> >> hoping that we could join forces with libclc at some point.
> >
> > This would be great if we could do this.
> 
> I have been following the recent additions to libclc adding
> high-accuracy math functions; this is where pocl's clc library is
> lacking. While all math functions should be there, they often do not
> have the required accuracies.
> 
> >> Compared to libclc, pocl should have more functionality, but the math
> >> functions are optimized for speed instead of accuracy.
> >>
> >
> > I'm not sure pocl has more functionality than libclc when it comes to
> > GPUs.  pocl uses __builtin functions for a lot of the math intrinsics which
> > expand to libm calls, but libm is not available on GPUs.
> 
> Apologies -- I indeed meant for CPUs. To my knowledge, pocl has not
> been used to target GPUs, although other accelerator-type devices are
> targeted as well.
> 
> -erik
> 
> > -Tom
> >> -erik
> >>
> >>
> >> On Tue, Sep 16, 2014 at 9:26 AM, He Junyan <junyan.he at inbox.com> 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?
> >> > 2. I find it is not compatible with OpenCL1.2, which Beignet must
> >> > support, are you going to implement it?
> >> > 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?
> >> >
> >> >
> >> > Thanks
> >> >
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > Libclc-dev mailing list
> >> > Libclc-dev at pcc.me.uk
> >> > http://www.pcc.me.uk/cgi-bin/mailman/listinfo/libclc-dev
> >>
> >>
> >>
> >> --
> >> Erik Schnetter <schnetter at cct.lsu.edu>
> >> http://www.perimeterinstitute.ca/personal/eschnetter/
> >>
> >> _______________________________________________
> >> 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