search for: libdevice

OK, I see the problem. You were right that we weren't picking up libdevice. CUDA 7.0 only ships with the following libdevice binaries (found /path/to/cuda/nvvm/libdevice): libdevice.compute_20.10.bc libdevice.compute_30.10.bc libdevice.compute_35.10.bc If you ask for sm_50 with cuda 7.0, clang can't find a matching libdevice binary, and it will apparently silent...

...../ -I/usr/local/cuda-7.0/samples/common/inc > >> --cuda-gpu-arch=sm_50 scalarProd.cu > >> > >> but ended up with the following error: > >> > >> ptxas fatal : Unresolved extern function '__nv_mul24' > >> > >> Seems to me that libdevice was not automatically linked. I wonder what > >> flags I need to pass to clang to have the code linked against libdevice? > >> > >> Thanks! > >> Yuanfeng Peng > >> _______________________________________________ > >> LLVM Developers mailing lis...

...as trying to compile scalarProd.cu (from CUDA SDK) with the following command: * clang++ -I../ -I/usr/local/cuda-7.0/samples/common/inc --cuda-gpu-arch=sm_50 scalarProd.cu* but ended up with the following error: *ptxas fatal : Unresolved extern function '__nv_mul24'* Seems to me that libdevice was not automatically linked. I wonder what flags I need to pass to clang to have the code linked against libdevice? Thanks! Yuanfeng Peng -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160729/ffdf3989/att...

...mand: >> >> clang++ -I../ -I/usr/local/cuda-7.0/samples/common/inc >> --cuda-gpu-arch=sm_50 scalarProd.cu >> >> but ended up with the following error: >> >> ptxas fatal : Unresolved extern function '__nv_mul24' >> >> Seems to me that libdevice was not automatically linked. I wonder what >> flags I need to pass to clang to have the code linked against libdevice? >> >> Thanks! >> Yuanfeng Peng >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.l...

...SDK) with the following > command: > > * clang++ -I../ -I/usr/local/cuda-7.0/samples/common/inc > --cuda-gpu-arch=sm_50 scalarProd.cu* > > but ended up with the following error: > > *ptxas fatal : Unresolved extern function '__nv_mul24'* > > Seems to me that libdevice was not automatically linked. I wonder what > flags I need to pass to clang to have the code linked against libdevice? > > Thanks! > Yuanfeng Peng > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.ll...

Does anyone know whether there is yet support for math functions in AMD GPU kernels? In the NVIDIA world they provide the libdevice IR module which can be linked to an existing module containing the kernel. In other words they provide all math functions on IR level. NVIDIA even claims that libdevice is actually device specific (compute capability). I was wondering how that is done on the AMD side of things. Thanks, Frank

...] Brian, this seems like a good question for you. On Wed, Nov 13, 2019 at 9:51 PM Frank Winter via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Does anyone know whether there is yet support for math functions in > AMD GPU kernels? > > In the NVIDIA world they provide the libdevice IR module which can be > linked to an existing module containing the kernel. In other words > they provide all math functions on IR level. NVIDIA even claims that > libdevice is actually device specific (compute capability). > > I was wondering how that is done on the AMD side of...

Thanks for the info! I would be glad to hear of any issues you have encountered on this path. I tried to make sure the 3.3 release was fully compatible with the libdevice implementation shipping with 5.5 (and as far as I know, it is). It's just not an officially supported configuration. Also, I've been meaning to address your -drvcuda issue. How would you feel about making that a part of the triple? On Wed, Jun 5, 2013 at 5:10 AM, Dmitry Mikushin <dm...

Dear all, FWIW, I've tested libdevice.compute_20.10.bc and libdevice.compute_30.10.bc from /cuda/nvvm/libdevice shipped with CUDA 5.5 preview. IR is compatible with LLVM 3.4 trunk that we use. Results are correct, performance - almost the same as what we had before with cicc-sniffed IR, or maybe <10% better. Will test libdevice.comp...

> The issue is really that there is no standard math library for PTX. Well, formally, that could very well be true. Moreover, in some parts CPU math standard is impossible to accomplish on parallel architectures, consider, for example errno behavior. But here we are speaking more about practical side. And the practical side is: past 5 years CUDA claims to accelerate compute applications, and

...lorenz.braun at ziti.uni-heidelberg.de -------------- next part -------------- #$ _SPACE_= #$ _CUDART_=cudart #$ _HERE_=/opt/cuda-8.0/bin #$ _THERE_=/opt/cuda-8.0/bin #$ _TARGET_SIZE_= #$ _TARGET_DIR_= #$ _TARGET_SIZE_=64 #$ TOP=/opt/cuda-8.0/bin/.. #$ NVVMIR_LIBRARY_DIR=/opt/cuda-8.0/bin/../nvvm/libdevice #$ LD_LIBRARY_PATH=/opt/cuda-8.0/bin/../lib:/opt/cuda-8.0/lib64:/opt/llvm-4.0/lib #$ PATH=/opt/cuda-8.0/bin/../open64/bin:/opt/cuda-8.0/bin/../nvvm/bin:/opt/cuda-8.0/bin:/opt/cuda-8.0/bin:/opt/llvm-4.0/bin:/home/lbraun/.opt/local/bin:/home/lbraun/.local/bin:/home/lbraun/.local/bin:/usr/local/bin:/u...

...name" " axpy.cu" "-mrelocation-model" "static" "-mthread-model" "posix" "-mdisable-fp-elim" "-fmath-errno" "-no-integrated-as" "-fcuda-is-device" "-mlink-cuda-bitcode" "/usr/local/cuda/nvvm/libdevice/libdevice.compute_35.10.bc" "-target-feature" "+ptx42" "-target-cpu" "sm_35" "-dwarf-column-info" "-debugger-tuning=gdb" "-resource-dir" "/usr/local/google/home/jingyue/Work/llvm/install-git/bin/../lib/clang/3.9.0"...

...-disable-free -disable-llvm-verifier -discard-value-names -main-file-name testparticles.cpp -mrelocation-model static -mthread-model posix -mdisable-fp-elim -no-integrated-as -fuse-init-array -fcuda-is-device -mlink-builtin-bitcode /net/gs/vol3/software/modules-sw/cuda/10.0/Linux/RHEL6/x86_64/nvvm/libdevice/libdevice.10.bc -target-feature +ptx61 -target-cpu sm_75 -dwarf-column-info -debug-info-kind=limited -dwarf-version=2 -debugger-tuning=gdb -v -resource-dir /home/aznb/.linuxbrew/Cellar/llvm/HEAD-48aefa8/lib/clang/9.0.0 -internal-isystem /home/aznb/.linuxbrew/Cellar/llvm/HEAD-48aefa8/lib/clang/9.0.0...

...-disable-free -disable-llvm-verifier -discard-value-names -main-file-name testparticles.cpp -mrelocation-model static -mthread-model posix -mdisable-fp-elim -no-integrated-as -fuse-init-array -fcuda-is-device -mlink-builtin-bitcode /net/gs/vol3/software/modules-sw/cuda/10.0/Linux/RHEL6/x86_64/nvvm/libdevice/libdevice.10.bc -target-feature +ptx61 -target-cpu sm_75 -dwarf-column-info -debug-info-kind=limited -dwarf-version=2 -debugger-tuning=gdb -v -resource-dir /home/aznb/.linuxbrew/Cellar/llvm/HEAD-48aefa8/lib/clang/9.0.0 -internal-isystem /home/aznb/.linuxbrew/Cellar/llvm/HEAD-48aefa8/lib/clang/9.0.0...

...-disable-free -disable-llvm-verifier -discard-value-names -main-file-name testparticles.cpp -mrelocation-model static -mthread-model posix -mdisable-fp-elim -no-integrated-as -fuse-init-array -fcuda-is-device -mlink-builtin-bitcode /net/gs/vol3/software/modules-sw/cuda/10.0/Linux/RHEL6/x86_64/nvvm/libdevice/libdevice.10.bc -target-feature +ptx61 -target-cpu sm_75 -dwarf-column-info -debug-info-kind=limited -dwarf-version=2 -debugger-tuning=gdb -v -resource-dir /home/aznb/.linuxbrew/Cellar/llvm/HEAD-48aefa8/lib/clang/9.0.0 -internal-isystem /home/aznb/.linuxbrew/Cellar/llvm/HEAD-48aefa8/lib/clang/9.0.0...

...-disable-free -disable-llvm-verifier -discard-value-names -main-file-name testparticles.cpp -mrelocation-model static -mthread-model posix -mdisable-fp-elim -no-integrated-as -fuse-init-array -fcuda-is-device -mlink-builtin-bitcode /net/gs/vol3/software/modules-sw/cuda/10.0/Linux/RHEL6/x86_64/nvvm/libdevice/libdevice.10.bc -target-feature +ptx61 -target-cpu sm_75 -dwarf-column-info -debug-info-kind=limited -dwarf-version=2 -debugger-tuning=gdb -v -resource-dir /home/aznb/.linuxbrew/Cellar/llvm/HEAD-48aefa8/lib/clang/9.0.0 -internal-isystem /home/aznb/.linuxbrew/Cellar/llvm/HEAD-48aefa8/lib/clang/9.0.0...

Ah, that's helpful. I knew that I'd need to end up with PTX as text, not a true binary, but I would have figured that it would come out of MCJIT. Thanks for helping to steer me away from the wrong trail. OK, one more question: Can anybody clarify the pros and cons of generating the PTX through the standard LLVM distro, versus using the "libnvvm" that comes with the Cuda SDK?

...uot; "-mrelocation-model" "static" "-mthread-model" "posix" >> "-mdisable-fp-elim" "-fmath-errno" "-no-integrated-as" "-fcuda-is-device" >> "-mlink-cuda-bitcode" >> "/usr/local/cuda/nvvm/libdevice/libdevice.compute_35.10.bc" >> "-target-feature" "+ptx42" "-target-cpu" "sm_35" "-dwarf-column-info" >> "-debugger-tuning=gdb" "-resource-dir" >> "/usr/local/google/home/jingyue/Work/llvm/install-git/b...

Hi Alexey, Thanks for the great work! The version I checked out works most of the time. But I do encounter crashes sometimes. I can't file a bug report on https://bugs.llvm.org/ because I don't have an account. I sent an email to bugs-admin at lists.llvm.org for an account already but I haven't heard back. Meanwhile, can you take a look at the issue? I'm attaching the bug report

...ssie. > tags 577190 + jessie Bug #577190 [gedit] gedit doesn't allow preferences change Added tag(s) jessie. > tags 616848 + jessie Bug #616848 [src:infon-devel] infon-devel: deprecation of dh_pycentral, please use dh_python2 Added tag(s) jessie. > tags 676272 + jessie Bug #676272 [src:libdevice-cdio-perl] libdevice-cdio-perl: FTBFS with perl 5.16: unknown type name 'bool' Added tag(s) jessie. > tags 600804 + jessie Bug #600804 [evolution-data-server] evolution-data-server: e-calendar-factory consumes 100% on every access to calendars (and then returns to normal) Added tag(s) je...