search for: compilecudawithllvm

...lt;code.kchoi at gmail.com> Sent: Wednesday, August 2, 2017 3:44 PM To: Xipeng Shen Cc: llvm-dev at lists.llvm.org Subject: Re: [llvm-dev] CUDA compilation "No available targets are compatible with this triple." problem I'm assuming you are following guide at https://llvm.org/docs/CompileCudaWithLLVM.html#compiling-cuda-code Compiling CUDA with clang — LLVM 6 documentation<https://llvm.org/docs/CompileCudaWithLLVM.html#compiling-cuda-code> llvm.org Prerequisites ¶ CUDA is supported in llvm 3.9, but it’s still in active development, so we recommend you compile clang/LLVM from HEAD. Before...

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 -...

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

...> llvm.org, since they would effectively be contributing dead code that the > community would have to maintain. > One data point (IIRC) is that the NVPTX backend sat in tree for a long time without a way to actually use them. But lately this has been opening up (e.g. http://llvm.org/docs/CompileCudaWithLLVM.html). However, the obstacle for NVPTX was mostly a software proprietary-ness (no way to plug it into the driver stack really, except via nvidia's own proprietary software), whereas the actual hardware was available. For the Lanai stuff, it seems like the hardware is fundamentally not available...

...nux distribution are you running, and what version?) We will also need the output of running your command with "clang -v" and the preprocessor output, clang -E. -Justin On Thu, Oct 27, 2016 at 11:49 AM, 李阳 <liyang.cs.cqu at gmail.com> wrote: > Yes, I am following the document `CompileCUDAWithLLVM.rst`. > > And I want to use the `clang++` to compile the CUDA program to generate > intermediate representation(IR). However what I have been trying is that > `nvcc` can compile correctly and `clang++` cannot. > > I dont know whether the `nvcc` can generate the IR code or PTX leve...

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...

..., 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 the example program > on https://llvm.org/docs/CompileCudaWithLLVM.html#invoking-clang > <https://llvm.org/docs/CompileCudaWithLLVM.html#invoking-clang.> -- > the error is: > > [aznb at asp testcuda]$ clang++ axpy.cu -g -o axpy --cuda-gpu-arch=sm_61 > -lcudart_static -ldl -lrt -pthread -v > clang version 9.0.0 (https://git.llvm.org/git/clan...

...Feb 9, 2016, at 4:18 PM, Sean Silva via llvm-dev < > llvm-dev at lists.llvm.org > wrote: > > > One data point (IIRC) is that the NVPTX backend sat in tree for a > long time without a way to actually use them. But lately this has > been opening up (e.g. http://llvm.org/docs/CompileCudaWithLLVM.html > ). However, the obstacle for NVPTX was mostly a software > proprietary-ness (no way to plug it into the driver stack really, > except via nvidia's own proprietary software), whereas the actual > hardware was available. For the Lanai stuff, it seems like the > hardware is f...

How can I or who should I talk with to add a sub-domain name? I just pushed in some doc <http://llvm.org/docs/CompileCudaWithLLVM.html> on compiling CUDA with LLVM. It would be good to have cuda.llvm.org for example point to that page. Jingyue -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20151110/b578635c/attachment.html>

...but who knows, it may be more complicated than that. Regards, -Justin On Wed, Oct 26, 2016 at 9:59 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/li...

Hi, I wonder whether the current version of LLVM supports separate compilation and linking of device code, i.e., is there a flag analogous to nvcc's --relocatable-device-code flag? If not, is there any plan to support this? Thanks! Yuanfeng Peng -------------- next part -------------- An HTML attachment was scrubbed... URL:

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>

So that people have a shorter link to go to that entry page directly. It's especially useful for non-LLVM folks who want to try out LLVM's CUDA support. Many researchers fall into this category btw because LLVM used to support very little CUDA. They don't like to search llvm.org for what they want. On Tue, Nov 10, 2015 at 2:59 PM, C Bergström <cbergstrom at pathscale.com> wrote:

Hi Arpith, That is exactly what it is :). My bad, I thought I copied over the libraries to where LIBRARY_PATH pointing but apparently it was copied to a wrong destination. Thanks a lot. On Wed, Jan 20, 2016 at 4:51 AM, Arpith C Jacob <acjacob at us.ibm.com> wrote: > Hi Ahmed, > > nvlink is unable to find the GPU OMP runtime library in its path. Does > LIBRARY_PATH point to

...d 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/CompileCudaWithLLVM.html#invoking-clang -- the error is: [aznb at asp testcuda]$ clang++ axpy.cu -g -o axpy --cuda-gpu-arch=sm_61 -lcudart_static -ldl -lrt -pthread -v clang version 9.0.0 (https://git.llvm.org/git/clang.git 4566ed0d7c076ad061168f7c6cb5fa3a793614a8) (https://git.llvm.org/git/llvm.git b7195a6d8d9064c4...

...n Feb 9, 2016, at 4:18 PM, Sean Silva via llvm-dev < > llvm-dev at lists.llvm.org > wrote: > > > One data point (IIRC) is that the NVPTX backend sat in tree for a > long time without a way to actually use them. But lately this has > been opening up (e.g. http://llvm.org/docs/CompileCudaWithLLVM.html > ). However, the obstacle for NVPTX was mostly a software > proprietary-ness (no way to plug it into the driver stack really, > except via nvidia's own proprietary software), whereas the actual > hardware was available. For the Lanai stuff, it seems like the > hardware is f...

...d 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/CompileCudaWithLLVM.html#invoking-clang -- the error is: [aznb at asp testcuda]$ clang++ axpy.cu -g -o axpy --cuda-gpu-arch=sm_61 -lcudart_static -ldl -lrt -pthread -v clang version 9.0.0 (https://git.llvm.org/git/clang.git 4566ed0d7c076ad061168f7c6cb5fa3a793614a8) (https://git.llvm.org/git/llvm.git b7195a6d8d9064c4...

...d 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/CompileCudaWithLLVM.html#invoking-clang -- the error is: [aznb at asp testcuda]$ clang++ axpy.cu -g -o axpy --cuda-gpu-arch=sm_61 -lcudart_static -ldl -lrt -pthread -v clang version 9.0.0 (https://git.llvm.org/git/clang.git 4566ed0d7c076ad061168f7c6cb5fa3a793614a8) (https://git.llvm.org/git/llvm.git b7195a6d8d9064c4...

...t; <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> One data point (IIRC) is that the NVPTX backend sat in tree for a >> long time without a way to actually use them. But lately this has >> been opening up (e.g. http://llvm.org/docs/CompileCudaWithLLVM.html). >> However, the obstacle for NVPTX was mostly a software >> proprietary-ness (no way to plug it into the driver stack really, >> except via nvidia's own proprietary software), whereas the actual >> hardware was available. For the Lanai stuff, it seems like the...

...d 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/CompileCudaWithLLVM.html#invoking-clang -- the error is: [aznb at asp testcuda]$ clang++ axpy.cu -g -o axpy --cuda-gpu-arch=sm_61 -lcudart_static -ldl -lrt -pthread -v clang version 9.0.0 (https://git.llvm.org/git/clang.git 4566ed0d7c076ad061168f7c6cb5fa3a793614a8) (https://git.llvm.org/git/llvm.git b7195a6d8d9064c4...