search for: moveparam

Displaying 4 results from an estimated 4 matches for "moveparam".

Did you mean: modparam
2013 Mar 22
2
[LLVMdev] UNREACHABLE executed! error while trying to generate PTX
...line given by you and I get the following error clang++ nbody.kernel.cu -Xclang -fcuda-is-device -I/home/upitamba/llvm-3.2.src/tools/clang/test/SemaCUDA/ -Xclang -triple -Xclang nvptx64 -Xclang -target-cpu -Xclang sm_10 -S fatal error: error in backend: Cannot select: 0x334a870: v4f32 = NVPTXISD::MoveParam 0x334a770 [ORD=1] [ID=22] 0x334a770: v4f32 = TargetExternalSymbol'.PARAM0' [ID=1] In function: computeBodyAccel Am I doing anything wrong here ? Attached my new nbody.kernel.cu <http://llvm.1065342.n5.nabble.com/file/n56141/nbody.kernel.cu> .cu here -- View this message in...
2013 Mar 24
0
[LLVMdev] UNREACHABLE executed! error while trying to generate PTX
...ollowing error > > clang++ nbody.kernel.cu -Xclang -fcuda-is-device > -I/home/upitamba/llvm-3.2.src/tools/clang/test/SemaCUDA/ -Xclang -triple > -Xclang nvptx64 -Xclang -target-cpu -Xclang sm_10 -S > > fatal error: error in backend: Cannot select: 0x334a870: v4f32 = > NVPTXISD::MoveParam 0x334a770 [ORD=1] [ID=22] > 0x334a770: v4f32 = TargetExternalSymbol'.PARAM0' [ID=1] > In function: computeBodyAccel > > Am I doing anything wrong here ? > > Attached my new nbody.kernel.cu > <http://llvm.1065342.n5.nabble.com/file/n56141/nbody.kernel.cu> .cu h...
2013 Mar 21
0
[LLVMdev] UNREACHABLE executed! error while trying to generate PTX
Not really. Clang does not have a way to annotate device vs. kernel functions in C/C++ mode. You're probably better off trying to use OpenCL or CUDA mode in clang. In the clang unit tests, there is a cuda.h header that provides very basic support for these keywords: tests/SemaCUDA/cuda.h If you compile as CUDA (use .cu extension, or "-x cuda") and use this header, you will have
2013 Mar 20
2
[LLVMdev] UNREACHABLE executed! error while trying to generate PTX
Thanks a lot Justin, I will remove the toolkit header. Just one last question..(maybe ;) ) If I do away with toolkit headers it says unknown type name '__device__'. Does this function qualifier have an alternative ? or I can just do away with ? -- View this message in context: http://llvm.1065342.n5.nabble.com/UNREACHABLE-executed-error-while-trying-to-generate-PTX-tp56026p56093.html