Displaying 3 results from an estimated 3 matches for "sm_53".
Did you mean:
sm_35
2016 Oct 27
3
problem on compiling cuda program with clang++
...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:367:12: fatal error: 'sys/cdefs.h' file not
found
# include <sys/cdefs.h>`.
And I find that 'sys/cdefs.h' is included in the directory
`/usr/include/a...
2016 Oct 27
0
problem on compiling cuda program with clang++
...e 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:367:12: fatal error: 'sys/cdefs.h' file not
> found
> # include <sys/cdefs.h>`.
>
> And I find that 'sys/cdefs.h' is included in th...
2016 Oct 27
0
problem on compiling cuda program with clang++
...ng++.
>> >
>> > 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:367:12: fatal error: 'sys/cdefs.h' file
>> > not
>> > found
>> > # include <sys/cdefs.h>`.
>> >
&...