similar to: [LLVMdev] Clang support for CUDA

Hi All, I am a newbie to GPU programming. I wonder if anyone can help me with using GPU in .Call in R. Basically, I want to write a function that calcuates the sum of two double type vectors and implement this using GPU. My final goal is to make such an implementation callable from R. (a) First, I wrote a R-C interface handles the R object using .Call (saved as VecAdd_cuda.c

I don't know from the nortest package, but it should ***always*** be the case that you test hypotheses H_0: The data have a normal distribution. vs. H_a: The data do not have a normal distribution. So if you get a p-value < 0.05 you can say that ***there is evidence*** (at the 0.05 significance level) that the data are not from a normal distribution. If the nortest package does

I'm developing packages with CUDA, and I'm running into a problem with memory allocation. Since CUDA involves memory on the GPU device it requires that the program handle memory allocation and deallocation separately from R. The simplest case of allocating a char and then deallocating causes a segmentation fault when R closes. Not on garbage collection but only on exit. Is there

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

My question is based on a project I have partially done, but there is still something I'm not clear. My goal is to create a R package contains GPU functions (some are from Nividia cuda library, some are my self-defined CUDA functions) My design is quite different from current R's GPU package, I want to create a R object (external pointer) point to GPU address, and run my GPU function

Well, I tried the command 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 =

That particular error is fixed in trunk, but with your code I'm now hitting a new issue. I'll get the fix in soon. On Fri, Mar 22, 2013 at 1:08 AM, upit <uday_pitambare at yahoo.com> wrote: > Well, I tried the command line given by you and I get the following error > > clang++ nbody.kernel.cu -Xclang -fcuda-is-device >

It's hard to tell what is wrong without a concrete example. E.g., what is the program you are instrumenting? What is the definition of the hook function? How did you link that definition with the binary? One thing suspicious to me is that you may have linked the definition of _Cool_MemRead_Hook as a host function instead of a device function. AFAIK, PTX assembly cannot be linked. So, if you

Hello, can anybody here explain what a Jonckheere-Terpstra test is and whether it is implemented in R? I just know it's a non-parametric test, otherwise I've no clue about it ;-( . Are there alternatives to this test? thanks for help, Arne

1. There is, I believe, some redundant code in the calculation of the test statistic in ks.test in the package ctest. Lines 34-37 of the code read x <- y(sort(x), ...) - (0:(n - 1))/n STATISTIC <- switch(alternative, two.sided = max(abs(c(x, x - 1/n))), greater = max(c(x, x - 1/n)), less = -min(c(x, x - 1/n))) Lines 35-37 could read

On Fri, Mar 4, 2016 at 5:50 PM, Yuanfeng Peng <yuanfeng.jack.peng at gmail.com> wrote: > Hi Jingyue, > > My name is Yuanfeng Peng, I'm a PhD student at UPenn. I'm sorry to bother > you, but I'm having trouble with gpucc in my project, and I would be really > grateful for your help! > > Currently we're trying to instrument CUDA code using LLVM 3.9, and

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

Hi, Have anybody recently built LLVM in Debug mode /within/ space requirements from the Getting Started doc? https://llvm.org/docs/GettingStarted.html#hardware > An LLVM-only build will need about 1-3 GB of space. A full build of LLVM and Clang will need around 15-20 GB of disk space. From my experience this numbers looks drastically low. On FreeBSD my recent builds consumed more than

Already outdated, but rounded ;) I literally just opened the 5yrs logo, changed the text and then done: inkscape -z -o logo/fish-10yrs.{png,svg} cp {logo,website}/fish-10yrs.svg and then updated the rest of the files. Signed-off-by: Martin Kletzander <mkletzan@redhat.com> --- Makefile.am | 2 + logo/fish-10yrs.png | Bin 0 -> 65790 bytes logo/fish-10yrs.svg |

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking