search for: libraires

...g so that it can find your headers, but who knows, it may > be more complicated than that. We don't use them for their GPU, so I don't know, but those kits are meant to be CUDA development boxes. The board setup process has an installer (JetPack) which gets all the drivers, headers and libraires for CUDA development. It should be just a matter of finding them and using with -isystem. cheers, --renato

...rs, but who knows, it may >> be more complicated than that. > > We don't use them for their GPU, so I don't know, but those kits are > meant to be CUDA development boxes. > > The board setup process has an installer (JetPack) which gets all the > drivers, headers and libraires for CUDA development. It should be just > a matter of finding them and using with -isystem. > > cheers, > --renato

...nter types and address spaces were not really well factored to use all of the helper and convenience routines available, and add ones where missing. Some helpers were added, but not always enough, and not always in time for some of the usages to reflect these helpers. 3) The updates to the broader libraires, especially the transforms and analysis libraries were never accompanied with test cases for those transforms or analyses to even sanity check the changes. A few of these had bugs spotted by inspection during post-commit review, but we don't even really know how many more might be lurking. 4)...

...aces were not really well factored to use all of the helper > and convenience routines available, and add ones where missing. Some > helpers were added, but not always enough, and not always in time for > some of the usages to reflect these helpers. > > 3) The updates to the broader libraires, especially the transforms and > analysis libraries were never accompanied with test cases for those > transforms or analyses to even sanity check the changes. A few of > these had bugs spotted by inspection during post-commit review, but we > don't even really know how many more mi...

Hi, it looks like you're compiling CUDA for an ARM host? This is not a configuration we have tested, nor is it something we have the capability of testing at the moment. You may be able to make it work by providing the appropriate -isystem flags to clang so that it can find your headers, but who knows, it may be more complicated than that. Regards, -Justin On Wed, Oct 26, 2016 at 9:59 PM,

Hello. I looked a bit closer at the dumps that appear now that wine starts wineboot at each run. The faulty app is winedevice.exe; I disabled it in libraires, and now I don't get any more exceptions on starting wine. What is this winedevice.exe? What is it purpose, and what functionalities am I losing by disabling it? Thanks. -- Fabrice DELENTE

...> be more complicated than that. > > > > We don't use them for their GPU, so I don't know, but those kits are > > meant to be CUDA development boxes. > > > > The board setup process has an installer (JetPack) which gets all the > > drivers, headers and libraires for CUDA development. It should be just > > a matter of finding them and using with -isystem. > > > > cheers, > > --renato > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161028/b...

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

...s were not really well factored to use all of the helper > and convenience routines available, and add ones where missing. Some > helpers were added, but not always enough, and not always in time for > some of the usages to reflect these helpers. > > 3) The updates to the broader libraires, especially the transforms and > analysis libraries were never accompanied with test cases for those > transforms or analyses to even sanity check the changes. A few of > these had bugs spotted by inspection during post-commit review, but we > don't even really know how many mor...