search for: clbuildprogram

Dear all, After a huge amount of time trying to install LLVM and Clang i could finally do it, so now im trying to use this tools for generating a bytecode, then apply it modular optimizations and then generate an executable to test the result. First, I only want to compile a project and execute it to see how it works, specifically this one:

...do that the .c file uses the .cl that i have compiled before > with clang and i do not know how to do it. > > > > This is an interesting question. Basically, in OpenCL you can build your > device program in a separate ways: > > > > 1. Use clCreateProgramFromSource + clBuildProgram: this is so-called > “online” compilation, when your device code is written in OpenCL C and its > compilation is performed in runtime (all stages like front-end, middle-end > optimizations and back-end, i.e. codegen to native code) > 2. Use clCreateProgramWithBinary + clBuil...

...iew, the frontend should be parameterised by only two (more or less) parameters: bitness (32/64) and endianness (little/big). How one can even guarantee e.g. that a calling convention for NVIDIA GPUs is appropriate for ATI GPUs? So using calling conventions too early on (e.g. between invoking the clBuildProgram() and clCreateKernel() API functions) is a path to implementation divergence, rather than standardisation. From: Nick Lewycky [mailto:nlewycky at google.com] Sent: 17 December 2010 22:16 > > If that's not enough, could you swing it around and maintain single > > named metadata n...

...ER_IR_NATIVE, target=..., opts=..., r_log=...) > at llvm/invocation.cpp:710 > #23 0x00007ffff6b0a371 in clover::program::build (this=this at entry=0x23a0530, devs=..., opts=opts at entry=0x7ffff793dc0d "", headers=...) > at core/program.cpp:63 > #24 0x00007ffff6af31c4 in clBuildProgram (d_prog=0x23a0538, num_devs=0, d_devs=0x0, p_opts=<optimized out>, pfn_notify=0x0, user_data=0x0) > at api/program.cpp:182 > > Does this look related? If so, let me know what other information you need to > try to debug this issue. This could be related; I'm not sure. I...

On Fri, Dec 17, 2010 at 04:21:18PM -0500, David Neto wrote: > However we record the fact that a function is a kernel, the mechanism > should handle the case of a kernel calling another kernel. > Recall that a kernel called by another kernel behaves more like a > regular function. For example it doesn't have workspace iteration > automatically applied to it; rather it just

The `Metadata`/`Value` split (PR21532) landed in r223802 -- at least, the C++ side of it. This was a rocky day, but I suppose that's what I get for failing to stage the change in smaller pieces. As of r223916 (lldb), I'm not aware of any remaining (in-tree) breakage, so if I've missed some problem in the sea of buildbot errors, please flag me down. I'll follow up soon with

...=..., r_log=...) >>> at llvm/invocation.cpp:710 >>> #23 0x00007ffff6b0a371 in clover::program::build (this=this at entry=0x23a0530, devs=..., opts=opts at entry=0x7ffff793dc0d "", headers=...) >>> at core/program.cpp:63 >>> #24 0x00007ffff6af31c4 in clBuildProgram (d_prog=0x23a0538, num_devs=0, d_devs=0x0, p_opts=<optimized out>, pfn_notify=0x0, user_data=0x0) >>> at api/program.cpp:182 >>> >>> Does this look related? If so, let me know what other information you need to >>> try to debug this issue. >> &gt...

...> at llvm/invocation.cpp:710 > >>>> #23 0x00007ffff6b0a371 in clover::program::build (this=this at entry=0x23a0530, devs=..., opts=opts at entry=0x7ffff793dc0d "", headers=...) > >>>> at core/program.cpp:63 > >>>> #24 0x00007ffff6af31c4 in clBuildProgram (d_prog=0x23a0538, num_devs=0, d_devs=0x0, p_opts=<optimized out>, pfn_notify=0x0, user_data=0x0) > >>>> at api/program.cpp:182 > >>>> > >>>> Does this look related? If so, let me know what other information you need to > >>>> try...

...tion.cpp:710 >>>>>>> #23 0x00007ffff6b0a371 in clover::program::build (this=this at entry=0x23a0530, devs=..., opts=opts at entry=0x7ffff793dc0d "", headers=...) >>>>>>> at core/program.cpp:63 >>>>>>> #24 0x00007ffff6af31c4 in clBuildProgram (d_prog=0x23a0538, num_devs=0, d_devs=0x0, p_opts=<optimized out>, pfn_notify=0x0, user_data=0x0) >>>>>>> at api/program.cpp:182 >>>>>>> >>>>>>> Does this look related? If so, let me know what other information you need to >&...