search for: libwfv

Displaying 6 results from an estimated 6 matches for "libwfv".

2013 Jan 31
3
[LLVMdev] LoopVectorizer in OpenCL C work group autovectorization
...be added to LLVM upstream (not to an OpenCL implementation only) eventually as generic loop vectorization routines. > In any case, since our own OpenCL driver is more of a proof-of-concept > implementation and not very robust, I'd be willing to give it a try to > integrate the current libWFV into pocl. This should boost performance > quite a bit for many kernels without too much effort ;). I just don't > know (yet) where to start - can you give me a hint, Pekka? I'm very glad to hear this! Luckily, the pocl code base has been modularized to allow easily switching the &qu...
2013 Jan 31
0
[LLVMdev] LoopVectorizer in OpenCL C work group autovectorization
...t; eventually as generic loop vectorization routines. I completely agree. > > > In any case, since our own OpenCL driver is more of a > > proof-of-concept > > implementation and not very robust, I'd be willing to give it a try > > to > > integrate the current libWFV into pocl. This should boost > > performance > > quite a bit for many kernels without too much effort ;). I just Ralf, Does this mean that you're close to releasing the new version? Thanks again, Hal > > don't > > know (yet) where to start - can you give me a hint...
2013 Feb 01
1
[LLVMdev] LoopVectorizer in OpenCL C work group autovectorization
Hi Hal, On 1/31/13 6:47 PM, Hal Finkel wrote: >>> In any case, since our own OpenCL driver is more of a >>> proof-of-concept >>> implementation and not very robust, I'd be willing to give it a try >>> to >>> integrate the current libWFV into pocl. This should boost >>> performance >>> quite a bit for many kernels without too much effort ;). I just > > Ralf, Does this mean that you're close to releasing the new version? It depends ;). The new version is already running in our OpenCL driver, which means...
2013 Jan 31
0
[LLVMdev] LoopVectorizer in OpenCL C work group autovectorization
...or instead focus more on things not required by WFV, such as handling reductions and other kinds of loop-carried dependencies. In any case, since our own OpenCL driver is more of a proof-of-concept implementation and not very robust, I'd be willing to give it a try to integrate the current libWFV into pocl. This should boost performance quite a bit for many kernels without too much effort ;). I just don't know (yet) where to start - can you give me a hint, Pekka? Cheers, Ralf On 1/25/13 10:54 PM, Pekka Jääskeläinen wrote: >> I am in favor of adding metadata to control differen...
2013 Jan 25
2
[LLVMdev] LoopVectorizer in OpenCL C work group autovectorization
> I am in favor of adding metadata to control different aspects of > vectorization, mainly for supporting user-level pargmas [1] but also for > DSLs. Before we start adding metadata to the IR we need to define the > semantics of the tags. "Parallel_for" is too general. We also want to control > vectorization factor, unroll factor, cost model, etc. These are used to
2013 Feb 01
0
[LLVMdev] LoopVectorizer in OpenCL C work group autovectorization
...7 PM, Hal Finkel wrote: > >>> In any case, since our own OpenCL driver is more of a > >>> proof-of-concept > >>> implementation and not very robust, I'd be willing to give it a > >>> try > >>> to > >>> integrate the current libWFV into pocl. This should boost > >>> performance > >>> quite a bit for many kernels without too much effort ;). I just > > > > Ralf, Does this mean that you're close to releasing the new > > version? > > It depends ;). The new version is already ru...