Sorry for not getting back to this as quickly as I had hoped. My machine
with nVidia hardware is at home and I haven't had much time in the las few
evenings to play with it. This may be the case through the weekend; we
shall see.
bulk88, I was not entirely sure what PERL_NO_GET_CONTEXT did. After
David Mertens wrote:
Sorry for not getting back to this as quickly as I had hoped. My
machine with nVidia hardware is at home and I haven't had much time in
the las few evenings to play with it. This may be the case through the
weekend; we shall see.
bulk88, I was not entirely sure what
David Mertens wrote:
Sorry for the rapid-fire. I'm up late and the ideas are only trickling
out.
It appears that the code doesn't think __cplusplus is defined. That is
odd. nvcc claims (or, it used to) that it always runs the code through
a C++ compiler at the end of the day, so why it
bulk88 -
nvcc knows about C, C++, and CUDA-C. I do not recall if it differentiates
between C and C++, though. I know that I correctly specify that Minimal.c
should be compiled as CUDA-C, but I'm not sure if I told it to do that in
the preprocessor command that produced the code I included in the
Hello everybody -
I recently resuscitated CUDA::Minimal, a module that provides basic memory
allocation and memory transfer functionality for CUDA (i.e. video card)
parallel programming. Note, you must write your own CUDA kernels
separately; I recommend writing them in XS wrapper code, using
David Mertens wrote:
Hello everybody -
I recently resuscitated CUDA::Minimal, a module that provides basic
memory allocation and memory transfer functionality for CUDA (i.e.
video card) parallel programming. Note, you must write your own CUDA
kernels separately; I recommend writing them in
Sorry, meant to reply-all.
David
-- Forwarded message --
From: David Mertens dcmertens.p...@gmail.com
Date: Mon, Feb 18, 2013 at 12:51 AM
Subject: Re: Apparent linkage conflicts with dVAR; dXSARGS; when compiled
using nvcc
To: bulk88 bul...@hotmail.com
bulk88 -
I've updated
