similar to: Segmentation Fault when using 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

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

Hi, I am trying to convert a simple CUDA program to LLVM IR using clang 3.0. The program is as follows, #include<stdio.h> #nclude<clang/test/SemaCUDA/cuda.h> __global__ void kernfunc(int *a) { *a=threadIdx.x+blockIdx.x*blockDim.x; } int main() { int *h_a,*d_a,n; n=sizeof(int); h_a=(int*)malloc(n); *h_a=5; cudaMalloc((void*)&d_a,n); cudaMemcpy(d_a,h_a,n,cudaMemcpyHostToDevice);

https://bugs.freedesktop.org/show_bug.cgi?id=111724 Bug ID: 111724 Summary: NVE6 (GK106) memory re-clocking breaks GpuTest plot3d benchmark Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: not set

I have looked at problem with Fermi GPUs where changing to higher clock led to really bad perfomance (with GpuTest 20x worse perfomance) and later also crashes of the nouveau. It seemed to be affected by Shader Clock in Voltage Entries in the video BIOS. Disabling BYPASS_PLL_CHECK in CLK0_CTRL seems to completely fix the issue. I have tried to search this BYPASS_PLL_CHECK in Nvidia traces but

I have looked at problem with Fermi GPUs where changing to higher clock led to really bad perfomance (with GpuTest 20x worse perfomance) and later also crashes of the nouveau. It seemed to be affected by Shader Clock in Voltage Entries in the video BIOS. Disabling BYPASS_PLL_CHECK in CLK0_CTRL seems to completely fix the issue. I have tried to search this BYPASS_PLL_CHECK in Nvidia traces but

To the noueau devs: Is there an appropriate list/forum to get support for nouveau, or is this the list? The nvidia support forums seem to be for the binary nvidia driver which I'm not running. On Mon, May 08, 2023 at 05:38:38PM -0500, Steven Kucharzyk wrote: > I understand parts of your motivation in how you want to deal with > Nvidia. Without knowing what you have or have not done in

hi Andrew Many thanks for the suggestion. I gave it a try , but still get the same issue - a fresh Rgui window (just one) opens, with an empty .RData, when I submit a script ( Ctrl & F8 ). I also tried running things as administrator, but it made no difference. Apparently windows 7 is selling like hot buns, so there should be enough market pressure before too long , to encourage the

I have looked at problem with Fermi GPUs where changing to higher clock led to really bad perfomance (with GpuTest 20x worse perfomance) and later also crashes of the nouveau. It seemed to be affected by Shader Clock in Voltage Entries in the video BIOS. Disabling BYPASS_PLL_CHECK in CLK0_CTRL seems to completely fix the issue. I have tried to search this BYPASS_PLL_CHECK in Nvidia traces but

I have looked at problem with Fermi GPUs where changing to higher clock led to really bad perfomance (with GpuTest 20x worse perfomance) and later also crashes of the nouveau. It seemed to be affected by Shader Clock in Voltage Entries in the video BIOS. Disabling BYPASS_PLL_CHECK in CLK0_CTRL seems to completely fix the issue. I have tried to search this BYPASS_PLL_CHECK in Nvidia traces but

# devtools The aim of `devtools` is to make your life as a package developer easier by providing R functions that simplify many common tasks. Devtools is opinionated about how to do package development, and requires that you use `roxygen2` for documentation and `testthat` for testing. Future version will relax these opinions - patches are welcome! You can track (and contribute to) development of

# devtools The aim of `devtools` is to make your life as a package developer easier by providing R functions that simplify many common tasks. Devtools is opinionated about how to do package development, and requires that you use `roxygen2` for documentation and `testthat` for testing. Future version will relax these opinions - patches are welcome! You can track (and contribute to) development of

I'm building a simple R extension around a CUDA-enabled dynamic library, and I want to run the whole package with cuda-memcheck for debugging purposes. I can run it just fine with Valgrind: $ R --no-save -d valgrind < test.R However, if I try the same thing with cuda-memcheck, $ R --no-save -d cuda-memcheck < test.R I get: *** Further command line arguments ('--no-save ')

On Wed, Apr 8, 2015 at 10:12 AM, Dmitry Mikushin <dmitry at kernelgen.org> wrote: > A tool of this kind here: https://github.com/apc-llc/nvcc-llvm-ir > > 2015-04-08 19:01 GMT+02:00 Ahmed ElTantawy <ahmede at ece.ubc.ca>: > >> Hi, >> >> I wanted to ask whether there is ongoing effort (or an already >> established tool) that enables to convert CUDA

cross-posting announcement to R-Announce, R-devel and R-package-devel. The R Consortium recently announced (https://www.r-consortium.org/news/blogs/2016/08/r-consortium-funds-three-projects-july) support of the R Documentation Task Force. The task force aims to design and implement the next generation documentation system for R. We aim to take the best from the many attempts to improve

Hi, I wanted to ask whether there is ongoing effort (or an already established tool) that enables to convert CUDA kernels (that uses CUDA specific intrinsics, e.g., threadId.x, __syncthreads(), ...) to LLVM IR. I am aware that I can do this for OpenCL with the help of libclc but I can not find something similar for CUDA. Thanks -------------- next part -------------- An HTML attachment was

Hi, I received an email from Nvidia, saying that llvm now supports ptx code generation. I am confused how to use llvm as my backend, as it seems clang's support for cuda is not complete yet. My question is: given a cuda program, how can I use llvm to generate ptx code? Thanks, Bo -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi: Does Clang support CUDA? I am looking for a front end for my compiler that can take CUDA programming framework. Thanks, -- *Abid ****************************************************** "I have learned silence from the talkative, toleration from the intolerant, and kindness from the unkind"---Gibran "Success is not for the chosen few, but for the few who choose" --- John

Nvidia previously announced open source LLVM CUDA compiler but now I couldn't find it anywhere. Can anyone help me to point out where I can download source code for playing with? Best Regards, Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120920/45d097d5/attachment.html>

Hi, I wonder whether the current version of LLVM supports separate compilation and linking of device code, i.e., is there a flag analogous to nvcc's --relocatable-device-code flag? If not, is there any plan to support this? Thanks! Yuanfeng Peng -------------- next part -------------- An HTML attachment was scrubbed... URL: