similar to: LIBCLC with LLVM 3.9 Trunk

It's not clear what is actually wrong from your original message, I think you need to give some more information as to what you are doing: Example source, what target GPU, compiler error messages or other evidence of "it's wrong" (llvm IR, disassembly, etc) ... -- Mats On 8 April 2016 at 09:55, Liu Xin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I built it

Hi all, I am hereby resigning my code ownership of libclc. I would like to nominate Tom Stellard as the new code owner. Thanks, -- Peter

Hi Chandler, Manuel, what's the right way to request/setup something like this? (automatic subscription of the libclc ML to all patches modifying files in llvm/libclc) thank you, Jan Vesely On Sat, Feb 15, 2020 at 12:01 AM Tom Stellard via Phabricator < reviews at reviews.llvm.org> wrote: > tstellar added a comment. > > In D74662#1877571

Hi Justin, I download llvm-ptx-samples [1] and try to build them. I found it seems lack of a complete document on how to build them with LLVM/Clang/libclc. Do you think it's a good idea to put a complete document/tutorial in _one_ place? Currently, there are your website [2], LLVM [3], Clang and libclc websites [5] over there. I feel people might get lost among those websites. ;-) Here

Do we have a list of these open-source LLVM-based OpenCL projects somewhere? Off the top of my head, we have: libclc: http://www.pcc.me.uk/~peter/libclc/ pocl: https://launchpad.net/pocl clover: http://cgit.freedesktop.org/~steckdenis/clover/ (I think that all of these have BSD- or MIT-style licenses). Are there any others? -Hal On Wed, 2011-10-19 at 14:47 +0100, Peter Collingbourne wrote:

Hi, My goal is to use Clang/LLVM/libclc to compile an OpenCL kernel and eventually generate a PTX code. I already did this but I am not sure if the PTX code I am generating is correct (is the one that is supposed to be generated). For example, currently, In OpenCL : get_global_id(0) translates to In LLVM : %call = tail call i32 @get_global_id(i32 0) which translates to In PTX:

Hi, This is to announce the availability of libclc, an open source, BSD licensed implementation of the library requirements of the OpenCL C programming language, as specified by the OpenCL 1.1 Specification. libclc is intended to be used with Clang's OpenCL frontend. libclc website: http://www.pcc.me.uk/~peter/libclc/ libclc is designed to be portable and extensible. To this end, it

Hi Ralf, > The project started as a use-case for our "Whole-Function Vectorization" > library, which allows to transform a function to compute the same as W > executions of the original code by using SIMD instructions (W = 4 for > SSE/AltiVec, 8 for AVX). Quite interesting. We were planning to add "vectorization" to our passes also, but if I understood the

Ralf, What version of the SDK were you using for your analysis? I don't see that in the slides/pdf. Thanks, Micah > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Ralf Karrenberg > Sent: Wednesday, October 19, 2011 2:13 PM > To: llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] ANN: libclc (OpenCL C

Hi Micah, The numbers from the paper were measured with the ATI Stream SDK v2.1 (it's only mentioned in the references I think). The most recent measurements I have were done with the current v2.5. Best, Ralf Am 19.10.2011 23:43, schrieb Villmow, Micah: > Ralf, > What version of the SDK were you using for your analysis? I don't see that in the slides/pdf. > > Thanks, >

Hi everybody, the compiler design lab at Saarland University (chair of Sebastian Hack) is also working on an LLVM-based OpenCL driver. The project started as a use-case for our "Whole-Function Vectorization" library, which allows to transform a function to compute the same as W executions of the original code by using SIMD instructions (W = 4 for SSE/AltiVec, 8 for AVX). The

Hi Carlos, On 10/20/11 9:54 AM, Carlos Sánchez de La Lama wrote: >> The project started as a use-case for our "Whole-Function Vectorization" >> library, which allows to transform a function to compute the same as W >> executions of the original code by using SIMD instructions (W = 4 for >> SSE/AltiVec, 8 for AVX). > > Quite interesting. We were planning to

Hello, I am the developer of Clover, and so much activity about OpenCL these days is really exciting. Here is my point of view, mainly on Clover and how the projects could use each other. Clover is made in a way that allow a certain level of modularity. Although POCL would be very difficult to merge into Clover (or Clover into POCL), as these two projects are nearly exactly doing the same things

Hi Peter, I'm assuming by this that you mean project ownership/maintainership of libclc, or are you instead referring to the copyright on your contributions to this project? I just want to be clear here. Also, do you plan on leaving the mailing list up, or should we start making alternative plans? Regards, Aaron Watry On Mon, Dec 8, 2014 at 3:18 PM, Peter Collingbourne <peter at

Hi, > which works but it produces LLVM IR code for all OpenCL intrinsics > implemented by libclc along with the kernel I am interested in, is their a > possibility to avoid this ? and only produce the llvm code for the kernel > required ? Mark all functions apart from the kernel entry points with the internal attribute and then run global dead code elimination (it should remove most

On Tue, Dec 6, 2011 at 10:17 PM, 陳韋任 <chenwj at iis.sinica.edu.tw> wrote: > Hi Justin, > > I download llvm-ptx-samples [1] and try to build them. I found it seems > lack > of a complete document on how to build them with LLVM/Clang/libclc. Do you > think > it's a good idea to put a complete document/tutorial in _one_ place? > Currently, > there are your

Hi, > libclc: http://www.pcc.me.uk/~peter/libclc/ > pocl: https://launchpad.net/pocl > clover: http://cgit.freedesktop.org/~steckdenis/clover/ I have pushed our implementation on GitHub: https://github.com/speziale-ettore/OpenCRun I have focused on desiging a modular system, because OpenCRun is intended to be used for research purpose -- not many people, no too much time, so clean

I was hoping you would come to the collaborative, joint solution. I've been waiting for Clang to have a settled OpenCL implementation to start working on OpenCL. Dealing with 3 parallel projects would be just that, a pain in the rear. - Marc On 10/20/2011 03:45 AM, Ralf Karrenberg wrote: > Hi Carlos, > > On 10/20/11 9:54 AM, Carlos Sánchez de La Lama wrote: >>> The

Hi, > If you have not already seen it, you (and anyone else working on > OpenCL runtimes) might be interested in this paper from AMD: > http://dl.acm.org/citation.cfm?id=1854302 > In particular, Section 4 describes the implementation approach for > their x86 OpenCL runtime and mentions a number of optimizations they > applied to things like the work-item stack. I know, but I

On Fri, Oct 21, 2011 at 9:48 AM, Speziale Ettore <speziale.ettore at gmail.com> wrote: > Currently I have implemented an OpenCL backend for i386 and X86_64 CPUs. > I have coded work-item stacks by hand because after some sintetic > benchmarks I have observed that both ucontext and setjmp/longjmp contain > some extra overheads. If you have not already seen it, you (and anyone