search for: compute_13

Hi, I'm trying to install a module - gputools - and keep getting compile time errors about missing R.h Does anyone know where this file can be found? Thanks!

...engine ( on CUDA Supported GPU) to execute the newly generated > assembly and copy back the result later. > I have to admit, I'm not sold on this solution. First, there is no clear way to pass codegen flags to the back-end. In PTX parlance, how would I embed an .ll file and compile to compute_13? Second, this adds a layer of obfuscation to the system. If I look at an .ll file, I expect to see all of the assembly in a reasonably clean syntax. If the device code is squashed into a constant array, it is much harder to read. Is the motivation for the intrinsic simply to preserve the abilit...

Hi LLVMers, The attached patch adds a new Intrinsic named "llvm.codegen" to support embedded LLVM IR code generation. **The 'llvm.codegen' intrinsic uses the LLVM back ends to generate code for embedded LLVM IR strings. The code generation target can be same or different to the one of the parent module. The original motivation inspiring us to add this intrinsic, is to

...GPU) to execute the newly >> generated assembly and copy back the result later. >> > > I have to admit, I'm not sold on this solution. First, there is no clear > way to pass codegen flags to the back-end. In PTX parlance, how would I > embed an .ll file and compile to compute_13? > We can handle this by provide a new argument (e.g. a string of properly-configured Target Machine) instead of or in addition to the Arch type string argument. > Second, this adds a layer of obfuscation to the system. If I look at an > .ll file, I expect to see all of the assembly in...

...cute the newly generated assembly and copy > back the result later. > > > I have to admit, I'm not sold on this solution. First, there is no > clear way to pass codegen flags to the back-end. In PTX parlance, > how would I embed an .ll file and compile to compute_13? > > We can handle this by provide a new argument (e.g. a string of > properly-configured Target Machine) instead of or in addition to the > Arch type string argument. I think we may in general discuss the additional information needed for the back ends and provide the information as...

...mbly and copy >> >> back the result later. >> >> >> I have to admit, I'm not sold on this solution. First, there is no >> clear way to pass codegen flags to the back-end. In PTX parlance, >> how would I embed an .ll file and compile to compute_13? >> >> We can handle this by provide a new argument (e.g. a string of >> properly-configured Target Machine) instead of or in addition to the >> Arch type string argument. >> > > I think we may in general discuss the additional information needed for > the bac...