search for: axpy

...pucc in my project, and I would be really > grateful for your help! > > Currently we're trying to instrument CUDA code using LLVM 3.9, and I've > written a pass to insert hook functions for certain function calls and > memory accesses. For example, given a CUDA program, say, axpy.cu, I > first compile it with > > clang++ -emit-llvm -c axpy.cu, > > which gives me two bitcode files, axpy.bc and axpy-sm_20.bc. Then I use > opt to load my pass and insert the hook functions to axpy.bc, which works > fine. After inspecting the instrumented axpy.bc, I notic...

...IR of your device code into one IR (via linking or direct IR emitting) before the IR to PTX. On Wed, Mar 9, 2016 at 4:31 PM, Yuanfeng Peng <yuanfeng.jack.peng at gmail.com> wrote: > Hi Jingyue, > > Thanks for the instructions! I instrumented the device code and got a > binary of axpy.cu; however, the resulting executable always fails on the > first cudaMalloc call in host code (the kernel had not even been launched > yet), with the error code being 30 (cudaErrorUnknown). In my > instrumentation pass, I only inserted a hook function upon each access to > device mem...

...quot; "-cc1" "-triple" "x86_64-unknown-linux-gnu" "-aux-triple" "nvptx64-nvidia-cuda" "-fcuda-target-overloads" "-fcuda-disable-target-call-checks" "-emit-obj" "-disable-free" "-main-file-name" "axpy.cu" "-mrelocation-model" "static" "-mthread-model" "posix" "-fmath-errno" "-masm-verbose" "-mconstructor-aliases" "-munwind-tables" "-fuse-init-array" "-target-cpu" "x86-64" "-mom...

...t;-triple" >> "x86_64-unknown-linux-gnu" "-aux-triple" "nvptx64-nvidia-cuda" >> "-fcuda-target-overloads" "-fcuda-disable-target-call-checks" "-emit-obj" >> "-disable-free" "-main-file-name" "axpy.cu" "-mrelocation-model" >> "static" "-mthread-model" "posix" "-fmath-errno" "-masm-verbose" >> "-mconstructor-aliases" "-munwind-tables" "-fuse-init-array" "-target-cpu" >> &q...

...gt; >>>> Hi Jingyue, >>>> >>>> Thank you so much for the helpful response! I didn't know that PTX >>>> assembly cannot be linked; that's likely the reason for my issue. >>>> >>>> So I did the following as you suggested(axpy-sm_30.bc is the >>>> instrumented bitcode, and cuda_hooks-sm_30.bc contains the hook functions): >>>> >>>> *llvm-link axpy-sm_30.bc cuda_hooks-sm_30.bc -o inst_axpy-sm_30.bc* >>>> >>>> *llc inst_axpy-sm_30.bc -o axpy-sm_30.s* >>>...

Hi all, I compiled the *llvm3.9* source code on the *Nvidia TX1* board. And now I am following the document in the docs/CompileCudaWithLLVM.rst to compile cuda program with clang++. However, when I compile `axpy.cu` using `nvcc`, *nvcc* can generate the correct the binary; while compiling `axpy.cu` using clang++, the detailed command is `clang++ axpy.cu -o axpy --cuda-gpu-arch=sm_53 -L/usr/local/cuda/lib64 -lcudart_static -ldl -lrt -pthread`, *clang++* generate the following error:`/usr/include/features.h...

Yes, I followed the guide. The same error showed up: >clang++ axpy.cu -o axpy --cuda-gpu-arch=sm_35 -L/usr/local/cuda/lib64 -I/usr/local/cuda/include -lcudart_static -ldl -lrt -pthread error: unable to create target: 'No available targets are compatible with this triple.' ________________________________ From: Kevin Choi <code.kchoi at gmail.com>...

Hi, I have trouble compiling CUDA code with Clang. The following is a command I tried: > clang++ axpy.cu -o axpy --cuda-gpu-arch=sm_35 --cuda-path=/usr/local/cuda The error message is error: unable to create target: 'No available targets are compatible with this triple.' The info of the LLVM I'm using is as follows: > lang++ --version clang version 6.0.0 (http://llvm.org/git/...

...I .prebuilts/ndk/current/sources/sources/cxx-stl/gnu-libstdc++/4.9/include \ -I prebuilts/ndk/current/sources/cxx-stl/gnu-libstdc++/4.9/libs/arm64-v8a/include \ -I ndk/sources/cxx-stl/system/include \ -L ./cuda/targets/aarch64-linux-androideabi/lib \ -lcudart -lcudart_static -ldl -lrt -pthread \ -o axpy axpy.cu clang version I am using is Android (4667116 based on r326829) clang version 7.0.1 ( https://android.googlesource.com/toolchain/clang 76e4d638afc560ad21845fad570888bef8c18045) ( https://android.googlesource.com/toolchain/llvm 67f3e6a51d93777841e0fb6d07f71fdf343df239) (based on LLVM 7.0.1sv...

Hi Char, I found the problem, for some reason the last patch was applied correctly. Just committed the fixed version. Tried to compile axpy.cu, everything works. ------------- Best regards, Alexey Bataev 23.01.2019 13:37, treinz пишет: > Hi Alexey, > > I tried the b7195a6 from the llvm github mirror, which does include > your commit D46189 <https://reviews.llvm.org/D46189> (see below). But > it can't compile...

Dear all, In the official document <https://llvm.org/docs/CompileCudaWithLLVM.html>, it is mentioned that CUDA compilation is supported on Windows as of 2017-01-05. I used msys2 to install clang 5.0.1. Then I installed cuda 8.0. However, I basically could not compile any code of cuda by the prescribed setting. I wounder if anyone can successfully compile cuda code by the clang on Windows.

.../cxx-stl/gnu-libstdc++/4.9/include > \ > -I > prebuilts/ndk/current/sources/cxx-stl/gnu-libstdc++/4.9/libs/arm64-v8a/include > \ > -I ndk/sources/cxx-stl/system/include \ > -L ./cuda/targets/aarch64-linux-androideabi/lib \ > -lcudart -lcudart_static -ldl -lrt -pthread \ > -o axpy axpy.cu > > clang version I am using is > Android (4667116 based on r326829) clang version 7.0.1 ( > https://android.googlesource.com/toolchain/clang > 76e4d638afc560ad21845fad570888bef8c18045) ( > https://android.googlesource.com/toolchain/llvm > 67f3e6a51d93777841e0fb6d07f71f...

...34-0410-b5e6-96231b3b80d8 I'll check this one out. Thanks, Char At 2019-01-24 03:01:18, "Alexey Bataev" <a.bataev at outlook.com> wrote: Hi Char, I found the problem, for some reason the last patch was applied correctly. Just committed the fixed version. Tried to compile axpy.cu, everything works. ------------- Best regards, Alexey Bataev 23.01.2019 13:37, treinz пишет: Hi Alexey, I tried the b7195a6 from the llvm github mirror, which does include your commit D46189 (see below). But it can't compile the example program on https://llvm.org/docs/CompileCudaWithLL...

...PM, 李阳 via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Hi all, > > I compiled the llvm3.9 source code on the Nvidia TX1 board. And now I am > following the document in the docs/CompileCudaWithLLVM.rst to compile cuda > program with clang++. > > However, when I compile `axpy.cu` using `nvcc`, nvcc can generate the > correct the binary; > > while compiling `axpy.cu` using clang++, the detailed command is `clang++ > axpy.cu -o axpy --cuda-gpu-arch=sm_53 -L/usr/local/cuda/lib64 > -lcudart_static -ldl -lrt -pthread`, clang++ generate the following > error...

...34-0410-b5e6-96231b3b80d8 I'll check this one out. Thanks, Char At 2019-01-24 03:01:18, "Alexey Bataev" <a.bataev at outlook.com> wrote: Hi Char, I found the problem, for some reason the last patch was applied correctly. Just committed the fixed version. Tried to compile axpy.cu, everything works. ------------- Best regards, Alexey Bataev 23.01.2019 13:37, treinz пишет: Hi Alexey, I tried the b7195a6 from the llvm github mirror, which does include your commit D46189 (see below). But it can't compile the example program on https://llvm.org/docs/CompileCudaWithLL...

Are you planning to release this as soon as it's ready or you want to make it into a major release? Is it possible to let me know (maybe by replying to this thread) once the code is ready? I know sometimes it takes a while to get things in the major release. I greatly appreciate your work on this! Thanks, Char 在 2018-12-15 05:19:50，"Alexey Bataev" <a.bataev at outlook.com>

...i all, >> > >> > I compiled the llvm3.9 source code on the Nvidia TX1 board. And now I am >> > following the document in the docs/CompileCudaWithLLVM.rst to compile >> > cuda >> > program with clang++. >> > >> > However, when I compile `axpy.cu` using `nvcc`, nvcc can generate the >> > correct the binary; >> > >> > while compiling `axpy.cu` using clang++, the detailed command is >> > `clang++ >> > axpy.cu -o axpy --cuda-gpu-arch=sm_53 -L/usr/local/cuda/lib64 >> > -lcudart_static -ld...

...34-0410-b5e6-96231b3b80d8 I'll check this one out. Thanks, Char At 2019-01-24 03:01:18, "Alexey Bataev" <a.bataev at outlook.com> wrote: Hi Char, I found the problem, for some reason the last patch was applied correctly. Just committed the fixed version. Tried to compile axpy.cu, everything works. ------------- Best regards, Alexey Bataev 23.01.2019 13:37, treinz пишет: Hi Alexey, I tried the b7195a6 from the llvm github mirror, which does include your commit D46189 (see below). But it can't compile the example program on https://llvm.org/docs/CompileCudaWithLL...

...34-0410-b5e6-96231b3b80d8 I'll check this one out. Thanks, Char At 2019-01-24 03:01:18, "Alexey Bataev" <a.bataev at outlook.com> wrote: Hi Char, I found the problem, for some reason the last patch was applied correctly. Just committed the fixed version. Tried to compile axpy.cu, everything works. ------------- Best regards, Alexey Bataev 23.01.2019 13:37, treinz пишет: Hi Alexey, I tried the b7195a6 from the llvm github mirror, which does include your commit D46189 (see below). But it can't compile the example program on https://llvm.org/docs/CompileCudaWithLL...

...34-0410-b5e6-96231b3b80d8 I'll check this one out. Thanks, Char At 2019-01-24 03:01:18, "Alexey Bataev" <a.bataev at outlook.com> wrote: Hi Char, I found the problem, for some reason the last patch was applied correctly. Just committed the fixed version. Tried to compile axpy.cu, everything works. ------------- Best regards, Alexey Bataev 23.01.2019 13:37, treinz пишет: Hi Alexey, I tried the b7195a6 from the llvm github mirror, which does include your commit D46189 (see below). But it can't compile the example program on https://llvm.org/docs/CompileCudaWithLL...