On Mittwoch 26 November 2008, Brad Zima wrote:
Reading more of the documentation showed that only certain datatypes may be
passed into the module, none of which are of int type. Is there something
I'm missing here? If not, is there a way to pass variables (i.e. image
width and image height)
Hi all,
Matthew Goodman reported (below) that PyCuda fails with CUDA 2.1 because nv
made a whitespace change in the cubin files they write. First of all, a change
like that shouldn't be able to take PyCuda down, so I've made sure that even
if metadata extraction fails, PyCuda doesn't throw
Hey Randy,
this here is the real problem:
On Freitag 05 Dezember 2008, Randy Heiland wrote:
cc1plus: error: unrecognized command line option -Wno-long-double
Somebody compiled your Python with -Wno-long-double, but your C++ compiler
does not understand that (warning-related, anyway) option.
Hi Jyh-Shyong,
On Sonntag 14 Dezember 2008, Jyh-Shyong Ho wrote:
I just installed pycuda-0.90.2 on my computer and I got the following
error message when I ran the program test_drive.py:
python test_drive.py
Traceback (most recent call last):
File test_driver.py, line 2, in module
On Montag 22 Dezember 2008, Jean-Christophe Penalva wrote:
Hello,
i try to install Pycuda on a host with python 2.4.
All is good (boost, numpy), until i fall on a problem during the make of
pycuda. There's a test on the version of python (for version = 2.5 ...),
and that break my
On Donnerstag 15 Januar 2009, Nicolas Pinto wrote:
- .def_readwrite(height, cl::Depth)
+ .def_readwrite(depth, cl::Depth)
Applied.
Andreas
signature.asc
Description: This is a digitally signed message part.
___
PyCuda mailing list
On Donnerstag 15 Januar 2009, Jozef Vesely wrote:
Hello,
I these random data do not seem very random ...
http://www.kolej.mff.cuni.cz/~vesej3am/transfer/plot.png
Moreover they are in [0, 0.5] range instead of [0, 1]
Working rand function would be very usefull.
I see that there's an issue,
Hey Nicholas,
On Freitag 30 Januar 2009, you wrote:
Attached is a slightly hacky patch for pycuda to enable reading of
source c files. Currently, includes must be in the same directory... I'm
not sure what the best policy is for dependencies; gcc -P -xc++ seems to
fail when encountering
On Samstag 31 Januar 2009, Nicholas Tung wrote:
Sure, no problem. Also, another question: how do I pass an offset from a
DeviceAllocation to a kernel? I can't seem to pass int's where it wants
pointers despite being able to cast DeviceAllocation to an int.
Two ways: wrap it in a numpy.intp--a
On Dienstag 10 Februar 2009, Peter Berrington wrote:
I didn't see any response on the mailing list so I thought I'd ask again.
Has anyone made any attempt at wrapping the cuda opengl interop functions
in pycuda? I've never used boost before and I'm not sure how to proceed.
I'd really like to
On Mittwoch 11 Februar 2009, Peter Berrington wrote:
Thanks a lot for working on that Andreas. I'd be more than happy to write a
tutorial/example and documentation, but I wasn't able to get it working
when I played around with it earlier today. I assume that I should first
call import
Hi Peter,
On Sonntag 01 März 2009, you wrote:
PyCuda looks very good - I'm excited to use it. But I found that I am
missing pytools, and I see no mention of it... anywhere. At least not in
the documents or on your home page..
What kind of failure do you get? (Please answer this even if the
On Mittwoch 18 März 2009, William King wrote:
I'm glad to help. I'd like to try to get a test together that will
compute some algorithm on the GPU and one on the CPU and compare the
speeds.
Do you think it would be possible to define the algorithm once, and
choose where it is executed?
On Mittwoch 18 März 2009, William King wrote:
Ok, for someone new to python(but very familiar with perl, java, php)
and new to CUDA. I have been able to setup my test enviroment and get
the test_driver.py and all to run properly.
I would like to help document(while I learn) how to use PyCuda
Hi all,
Exciting news! I've just committed code to do reductions into PyCUDA's git.
Sums and inner products are available now. Norms, maxima, minima and many
other things can be added with only a few lines of code. (Any takers? :)
Here's the code:
Hi all,
Another piece of niceness just landed in PyCUDA git: Semi-transparent support
for double-precision textures. This code papers over the complications and
differences between floats and doubles as far as texturing is concerned.
Here's how you use it.
Device-side:
8
On Mittwoch 08 April 2009, Andreas Klöckner wrote:
Host-side, everything should be transparent if you use
http://documen.tician.de/pycuda/array.html#pycuda.gpuarray.GPUArray.bind_to
_texref_ext to bind a GPUArray to the texture reference. Note: only
single-channel textures are supported
On Samstag 11 April 2009, Randy Heiland wrote:
Just curious - what does the warning mean?
There was a stray __global__ in that code, which I presume was an attempt to
get rid of the two advisories. Turns out that in certain situations there
appears to be no way of telling nvcc what kind of
Hi there,
here are a few comments on your truly heroic effort. :)
On Mittwoch 15 April 2009, B3design.jp wrote:
4.compiled Boost C++ libraries by mingw
type commandPrompt
cd c:\program files\boost\boost_1_38_0
bjam.exe --toolset=gcc --build-type=complete stage
I wait for huge time...
Whoops--this should've gone to the list.
Andreas
---BeginMessage---
Hi Nicholas,
(first off sorry for misspelling your name earlier)
On Freitag 03 April 2009, you wrote:
The shape argument for numpy.empty() can be a scalar for creation of
1-D arrays. If you refer to numpy documentation
On Samstag 25 April 2009, you wrote:
Hello,
Thank you all for your help.
Upon further investigation, it seems that it is not PyCuda's fault.
Eric4.4.4 seems to be unhappy with PyCuda. Eric4.4.3 works fine. If you
would stil like to read about it, the details are below.
This is somewhat
On Montag 27 April 2009, Matt G wrote:
Quick fix is using python2.5. It looks like python2.6 is the default that
python is hooked to under Jaunty. They made some changes to subprocess I
don't have time dig into, but it is causing problems with some of my code
as well. Also notably, if you
On Mittwoch 29 April 2009, Brent Pedersen wrote:
hi, i've never tried cuda or pycuda before, but i'm trying now on a
clean system with ubuntu 9.04.
i downloaded the install script for linux-64 ubuntu 8.04 here:
http://www.nvidia.com/object/cuda_get.html
will that work for 9.04? must one wait
I see one potential issue:
b_gpu = cuda.mem_alloc(len(h_OptionData))
You probably mean len(h_OptionData)*numpy.dtype(numpy.float32).itemsize,
which is a long way of saying len(h_OptionData)*4.
Word of advice: Use gpuarrays. Less foot-shooting potential.
Andreas
On Mittwoch 29 April 2009,
On Mittwoch 29 April 2009, Brent Pedersen wrote:
i dont have _internal.so maybe that's the prob, i have this:
Ah, sorry. _driver.so is correct. My bad.
$ ldd
/usr/lib/python2.5/site-packages/pycuda-0.92-py2.5-linux-x86_64.egg/pycuda/
_driver.so linux-vdso.so.1 = (0x7fffdc3fe000)
On Freitag 08 Mai 2009, Andrew Wagner wrote:
Hello-
Is there a recipe out there for getting PyCUDA (including
dependencies!) up and running that is known to just work?
I'm hopeful that if I can get PyCUDA installed properly, it will
become my primary research tool. I used MATLAB
On Freitag 08 Mai 2009, Andrew Wagner wrote:
Thanks! I pulled out my second graphics card and now I'm trying a
fresh install of Debian Lenny.
What version of CUDA do you recommend, and how did you install it?
The installation directions say you developed against CUDA 2.0 beta;
should I go
On Sonntag 10 Mai 2009, Vincent Favre-Nicolin wrote:
On dimanche 10 mai 2009, Andreas Klöckner wrote:
Try the command
$ ldd /usr/local/lib/python2.6/dist-packages/pycuda-0.93rc1-py2.6-linux-
x86_64.egg/pycuda/_driver.so
and see if you're inadvertently linking against a CUDA 2.1
You're a bit confused about whether you're passing in a *pointer* to an array
or the actual array data. The C struct says pointer to, your packing code says
inlined array.
I'd suggest checking out numpy record arrays.
Andreas
On Sonntag 10 Mai 2009, Per B. Sederberg wrote:
Hi Folks:
I'm
= []
CUDADRV_LIBNAME = ['cuda']
CXXFLAGS = []
LDFLAGS = []
Thanks Andreas! Now the real fun begins!
On Fri, May 8, 2009 at 4:42 PM, Andreas Klöckner
li...@informa.tiker.net wrote:
On Freitag 08 Mai 2009, Andrew Wagner wrote:
Thanks! I pulled out my second graphics card and now I'm trying
Hi Nicholas,
On Freitag 15 Mai 2009, you wrote:
I think the CU_DEVICE_ATTRIBUTE_COMPUTE_MODE is new in 2.2 so it
shouldn't be blindly included (also CU_COMPUTEMODE_DEFAULT,
CU_COMPUTEMODE_EXCLUSIVE, CU_COMPUTEMODE_PROHIBITED).
I don't think they are--these here are the only hits for git
Hi Bill,
sorry for the delay. What you reported is indeed a bug. I relied on a non-
standard member of std::vector in some code that was newly added. Should be
fixed in git. Please test and confirm it's fixed.
Thanks,
Andreas
On Freitag 15 Mai 2009, Bill Punch wrote:
I installed the CUDA 2.2
On Dienstag 19 Mai 2009, Bryan Catanzaro wrote:
I was browsing the documentation and saw the note that
pycuda.driver.Function.registers, etc. are deprecated and will be
removed in PyCuda 0.94. That makes me a little sad, as that
information is very useful to one of the projects I'm working
On Mittwoch 20 Mai 2009, Eli Bressert wrote:
CUDA_ROOT = '/user/local/cuda'
^^ Typo?
Andreas
signature.asc
Description: This is a digitally signed message part.
___
PyCuda mailing list
PyCuda@tiker.net
Try adding
CXXFLAGS = ['-DBOOST_PYTHON_NO_PY_SIGNATURES']
to your siteconf.py. That may help work around the ICE.
Andreas
On Mittwoch 20 Mai 2009, Hua Wong wrote:
I think Boost was well installed (no skip at all so...)
Cuda toolkit is installed
I don't know if I am doing something wrong in
On Donnerstag 21 Mai 2009, Paul Rigor (uci) wrote:
Hi Andreas,
Do you foresee PyCUDA extending support to the OpenCL standard?
It would probably happen as a separate package, but the thought of having
something for CL in the same spirit as PyCUDA has certainly crossed my mind. I
have a little
On Samstag 23 Mai 2009, Eli Bressert wrote:
Hi,
I was trying to use the cumath functions and ran into an error. I'm on
OS X 10.5.7 with a GeForce 8800GT graphics card and using
PyCUDA-0.93rc2. Am I doing something wrong or is there a bug? I did
not have this issue with PyCUDA -0.92.
A bug.
On Samstag 23 Mai 2009, Thomas Robitaille wrote:
Hello,
I am trying to sum a GPU array along one axis only. This can be done
in numpy:
a = np.random.random((100,200))
b = np.sum(a,axis=1)
However, there is no axis= keyword for the pycuda.gpuarray.sum()
method. Would this be simple to
On Mittwoch 20 Mai 2009, Bryan Catanzaro wrote:
Would it be possible to change both the Device.get_attribute() and the
Function.get_attribute() calls to make them Python attributes instead
of using function-and-flag? It seems like this could avoid the
inconsistency between the two.
I agree
On Dienstag 26 Mai 2009, Hua Wong wrote:
Sorry to bother again, I managed to pass the 'make' phase but I am now
stuck in the 'make install' one.
I guess it is using setup.py to install all the files that are made
during the Make process.
But I doesn't have the root privilege. And when I
Hi all,
Since there were a few issues reported with 0.93rc2, I've just rolled 0.93rc3.
Here's to hoping this version will also be 0.93. To make sure we get a solid
0.93 out, please test:
http://pypi.python.org/pypi/pycuda/0.93rc3
Thanks for all your dedication in reporting issues in these
On Sonntag 24 Mai 2009, Andreas Klöckner wrote:
Here's something that somehow feels like a second-best solution, but it at
least maintains consistency: Everything that can be accessed as
something.get_attribute(some.scope.ATTR_NAME)
can now *also* be accessed as
something.attr_name
On Sonntag 31 Mai 2009, Vince Fulco wrote:
get the error, ImportError:
/usr/lib64/python2.5/site-packages/pycuda-0.93rc3-py2.5-linux-x86_64.egg/py
cuda/_driver.so: undefined symbol: cuMemHostAlloc.
This means you're picking up a libcuda.so from CUDA 2.1. Try running
$ ldd
On Dienstag 02 Juni 2009, Marcel Krause wrote:
Hello list,
I try to install PyCUDA von WinXP SP 3. Most of the problems were
solved with a little editing:
* updating the DEFAULT_VERSION in ez_setup.py
This'll be unnecessary once 0.93 is out. Thanks for the reminder, though.
* let setup.py
On Mittwoch 03 Juni 2009, Marcel Krause wrote:
Hello Andreas, hello list,
You BOOST_PYTHON_LIBNAME is likely wrong--it refers to gcc,
and you're compiling with msvc.
thanks, I fixed it to boost_python-vc90-mt. There's only a file
libboost_python-vc90-mt.lib in the path I have as
On Freitag 05 Juni 2009, Chris Heuser wrote:
The boost warning worked. But I am confused, since I have version 1.37 of
boost installed. I will install 1.39, but 1.37 should work, shouldn't it?
My guess here is that you installed 1.37 manually, and you also have an old
set (maybe 1.34)
On Montag 08 Juni 2009, Adlar Kim wrote:
Hi,
After pycuda installation I ran some examples provided. Every time I
run them, I get the following message:
/usr/lib/python2.4/site-packages/pytools-9-py2.4.egg/pytools/
diskdict.py:119: UserWarning: DiskDict will memory-only: a usable
version
On Dienstag 09 Juni 2009, Adlar Kim wrote:
Hi,
I'm getting the following error when I try to build pycuda-0.93rc.
Could anybody help? Thanks.
I think I fixed [1] this a couple days ago. I just rolled 0.93rc4, which you
can get at [2]. AFAICT, your problem is specific to CUDA 2.1. Please try
Hi Massimo,
I'm mostly clueless about Macs, but I did notice that you built PyCUDA for the
32-bit ABI. Maybe Boost got built against the 64-bit one?
CXXFLAGS = ['-arch','i386']
LDFLAGS = ['-arch','i386']
(Btw, my suspicion is that these shouldn't be needed because PyCUDA (or rather
First off, if you have support questions, please go via the PyCUDA mailing
list. I've CC'ed them on this reply.
On Freitag 12 Juni 2009, you wrote:
Hello Andreas, I'm Luiz from Brazil.
BOOST_COMPILER was introduced in the 0.93 release cycle--the instructions
you're following do not match the
blank and things work fine for me (OSX 10.5).
-Randy
On Jun 12, 2009, at 8:27 AM, Andreas Klöckner wrote:
Hi Massimo,
I'm mostly clueless about Macs, but I did notice that you built PyCUDA
for the
32-bit ABI. Maybe Boost got built against the 64-bit one?
CXXFLAGS = ['-arch
On Samstag 13 Juni 2009, Andrew Wagner wrote:
Thanks again, Nicolas! I suspected that was the case...
If this is still the case in the latest pycuda, the documentation for
get_global() at
http://documen.tician.de/pycuda/driver.html#code-on-the-device-modules-and-
functions
needs to be
On Dienstag 09 Juni 2009, Adlar Kim wrote:
Hi,
I'm getting the following error when I try to build pycuda-0.93rc.
Could anybody help? Thanks.
Did 0.93rc4 work for you? If so, that would be one data point to help me
figure out if we're ready for 0.93.
Thanks,
Andreas
signature.asc
/wrap_cudadrv.cpp:310: error: ârnExâ was not declared in
this scope
src/wrapper/wrap_cudadrv.cpp: In function â:
src/wrapper/wrap_cudadrv.cpp:357: error: ârnExâ was not declared in
this scope
error: command 'gcc' failed with exit status 1
On Jun 15, 2009, at 12:13 PM, Andreas Klöckner wrote
On Montag 15 Juni 2009, you wrote:
I've attached a slightly
cleaned up, standalone version with NVIDIA's copyright notice
restored.
I'm assuming you meant for this to end up in PyCUDA's examples folder. That's
where it is now, in any case. :) Let me know if that wasn't the intenion.
Thanks
On Donnerstag 18 Juni 2009, ashleigh baumgardner wrote:
I did add the lib location to my .profile and that didn't fix all of my
problems but it put me on the right track. At this point PyCUDA does
compile, by which I mean make install does not give any errors. But when
I try to run the test
On Donnerstag 18 Juni 2009, Marcel Krause wrote:
Hello Andreas, hello list,
Nope--CUDA_ROOT's not a list. :)
thanks, that did it. In my first try, I got
/usr/bin/ld: cannot find -llibboost_python-gcc43-mt-1_39
Then I removed the prefix lib from BOOST_PYTHON_LIBNAME and
On Freitag 19 Juni 2009, Marcel Krause wrote:
Hello Andreas, hello list,
Also, since the second try, I am unable to reproduce the first
message about /usr/bin/ld.
The one that you fixed by removing lib? Or which other message are
you referring to?
Yes, that one. I'll try and write a
On Dienstag 30 Juni 2009, Michael Rule wrote:
Ok, fixed that ( needed to use uint not uint32. Numpy basic types
don't seem to be anywhere near the surface of Google and are hard to
find ). I now have another related question :
the documentation for the pycuda prepare function states
setting
On Donnerstag 02 Juli 2009, faberx wrote:
Dear all! You can install pycuda on windows xp! Please look at:
http://wiki.tiker.net/PyCuda/Installation/Windows
http://wiki.tiker.net/PyCuda/Installation/Windows
Thanks for writing this up!
Andreas
signature.asc
Description: This is a digitally
On Mittwoch 01 Juli 2009, Andreas Klöckner wrote:
Would you mind adding FAQ items for these two?
http://wiki.tiker.net/PyCuda/FrequentlyAskedQuestions
Thanks for writing the FAQ item! FYI--I've slightly reworked and expanded it.
http://is.gd/1mMDg
Andreas
signature.asc
Description
On Freitag 31 Juli 2009, Ahmed Fasih wrote:
Hi, I'm very surprised that google isn't turning up something about
this topic because I thought it's been previously discussed, so my
apologies if it has.
I'm trying the NVIDIA CUDA Visual Profiler (v 2.2.05) in Windows XP
with a fairly recent
On Mittwoch 12 August 2009, Andrew Wagner wrote:
Hi-
Is there a way to get a list of the global variables, especially
constant arrays and texture refs that are defined in a kernel?
I'm generating a pycuda.driver.Module from a template, and the storage
of various kernel inputs depends on the
On Mittwoch 12 August 2009, wtftc wrote:
I've updated the wiki with my configuration of Windows Vista 64 bit with
Visual Studio 2008. To use it, your entire python stack must also be 64
bit. The build was x64, also known as amd64.
Thanks!
I also have a question: is it possible to statically
On Mittwoch 12 August 2009, Ryan May wrote:
Hi,
I was trying to install pycuda today from source (in advance of the Scipy
tutorial!), and have noticed a problem if I don't use eggs to install. If
I use:
python setup.py install --single-version-externally-managed --root=/
I get the pycuda
On Montag 17 August 2009, Christian Quaia wrote:
Hi.
I've been trying to install pycuda on my centos 5.3 box, but I haven't had
much success. I managed to install boost (1.39) as per instructions, but
when I build pycuda I get the following error:
building '_driver' extension
gcc -pthread
That says that you're linking against the boost you built with gcc 4.3--
rebuild boost with 4.1, that you should get you a step further.
Andreas
On Dienstag 18 August 2009, Christian Quaia wrote:
Thanks Andreas.
Sorry, I should have tried that before... Now the build and install
work.
On Donnerstag 17 September 2009, mailboxalpha wrote:
I looked for DLL files used in _driver.pyd and one of them is named
nvcuda.dll. There is no such file on my machine. Perhaps that is the DLL
file that could not be found. The required boost dlls have been copied to
windows\system32
Hi all,
If you are attending Nvidia's GPU Technology Conference next week, there are
two things I'd like to point out:
- I'll be giving a talk about PyCUDA on Friday, October 2 at 2pm, where I'll
both introduce PyCUDA and talk about some exciting new developments. The talk
will be 50 minutes
On Mittwoch 23 September 2009, Andreas Klöckner wrote:
Hi all,
If you are attending Nvidia's GPU Technology Conference next week, there
are two things I'd like to point out:
- I'll be giving a talk about PyCUDA on Friday, October 2 at 2pm, where
I'll both introduce PyCUDA and talk about
Hi Roberto,
On Freitag 02 Oktober 2009, Roberto Vidmar wrote:
I wonder if it is possible to use PyCUDA to grid on a two dimensional
regular grid xyz scattered data. Our datasets are usually quite large
(some millions of points) .
Many thanks for any help in this topic.
As usual, if
Hi all,
--
This is relevant to you if you are using Python 2.6.3 and you are getting
errors of the sort:
/usr/local/lib/python2.6/dist-packages/setuptools-0.6c9-
py2.6.egg/setuptools/command/build_ext.py,
line 85, in
On Donnerstag 15 Oktober 2009, Andreas Klöckner wrote:
Hi all,
--
This is relevant to you if you are using Python 2.6.3 and you are getting
errors of the sort:
/usr/local/lib/python2.6/dist-packages/setuptools-0.6c9
On Donnerstag 15 Oktober 2009, Darcoux Christine wrote:
Hi Andreas
0.93.1rc1 seems to works for me, except that I had to download a
distribute_setup.py file. Could you include that file in the source
tarball ? I think this is the usual way to work with Distribute, since
the
On Montag 19 Oktober 2009, Michael Rule wrote:
I'm convinced that I need a prefix scan that gives me access to the
resultant prefix scanned array.
so, for example, using addition, I would like a function that takes :
1 1 1 1 1 1 1 1 1 1
to
0 1 2 3 4 5 6 7 8 9
It seems like this data
On Montag 26 Oktober 2009, Robert Manning wrote:
PyCUDA users,
I've been trying to find how to use pitch 2D linear memory textures
in pyCUDA and have been unsuccessful. I've seen C code that uses
cudaBindTexture2D and similar functions but it is not accessible (to
my knowledge) by pyCUDA.
Hi Maarten,
On Dienstag 03 November 2009, you wrote:
i've been using your pycuda package to play with, and I really like
it! much more productive than compiling etc..
I have pycuda installed with --single-version-externally-managed and a
different prefix. This causes pycuda not to find the
On Donnerstag 12 November 2009, Jonghwan Rhee wrote:
Hi there,
I have tried to install pycuda on opensuse 11.1. However, when I did
build, the following error occurred.
What version of Boost do you have, how and where was it installed?
Andreas
signature.asc
Description: This is a
not currently exist. Please create it and try again,
or choose a different installation directory (using the -d or
--install-dir option).
make: *** [install] Error 1
Jong
On Sat, Nov 14, 2009 at 12:51 PM, Andreas Klöckner
li...@informa.tiker.netwrote:
On Freitag 13 November 2009
On Freitag 20 November 2009, James Bergstra wrote:
Now that we're taking more advantage of PyCUDA's and CodePy's ability
to generate really precise special-case code... I'm finding that we
wind up with a lot of ambiguities about *which* generator should
handle a given special case. The right
On Freitag 20 November 2009, Janet Jacobsen wrote:
Hi, Andreas. I ran
ldd /usr/common/usg/python/2.6.4/lib/python2.6/site-packages
/pycuda-0.93.1rc2-py2.6-linux-x86_64.egg/pycuda/_driver.so
and got
libboost_python.so.1.40.0 =
On Samstag 21 November 2009, Wolfgang Rosner wrote:
Hello, Andreas Klöckner,
I can't get pycuda to build on my box.
I tried at least 10 times, try to reproduce details now.
In the archive, there was a similar thread with a SuSE 11.1 64 bit box ,
posted by Jonghwan Rhee
http
On Samstag 21 November 2009, Wolfgang Rosner wrote:
OK, for me it works now, but peomple might be even more (and earlier) happy
if the pytools issue had been mentioned in the setup wiki.
Pytools should be installed automatically along with 'python setup.py
install'. If it didn't: do you have
On Samstag 21 November 2009, Wolfgang Rosner wrote:
Pytools should be installed automatically along with 'python setup.py
install'. If it didn't: do you have any idea why?
not sure.
could it be that I ran make install
instead of python setup.py install ?
make install invokes python
On Sonntag 22 November 2009, you wrote:
Now this error:
python test_driver.py
Traceback (most recent call last):
File test_driver.py, line 481, in module
from py.test.cmdline import main
ImportError: No module named cmdline
Again, py.test should have been installed automatically for
Hey Bryan,
On Montag 23 November 2009, Bryan Catanzaro wrote:
I built 64-bit versions of Boost and PyCUDA on Mac OS X Snow Leopard, as
well as the 64-bit Python interpreter supplied by Apple, as well as the
CUDA 3.0 beta. Everything built fine, but when I ran pycuda.autoinit, I
got an
On Mittwoch 25 November 2009, Ken Seehart wrote:
Something like this came up for someone else in May:
http://www.mail-archive.com/pycuda@tiker.net/msg00361.html
*SystemError: ../Objects/longobject.c:336: bad argument to internal
function*
buf = struct.pack(format, *arg_data)
I fixed it
On Freitag 04 Dezember 2009, Bryan Catanzaro wrote:
Thanks for the explanation. In that case, do you have objections to
removing the assertion that if a GPUArray is created and given a
preexisting buffer, that the new array must be a view of another array?
In my situation, I don't think
On Dienstag 08 Dezember 2009, you wrote:
It's the first time I've installed the drivers, so I don't have multiple
versions. Anyway how can I know the versions of the headers used in the
compilation?
pycuda.driver.get_version()
pycuda.driver.get_driver_version()
Andreas
signature.asc
On Montag 14 Dezember 2009, Robert Cloud wrote:
Traceback (most recent call last):
File stdin, line 1, in module
pycuda._driver.LogicError: cuModuleGetFunction failed: not found
The problem is that nvcc compiles code as C++ by default, which means it uses
name mangling [1].
If you don't
On Freitag 18 Dezember 2009, Dan Piponi wrote:
I have no problem making a struct in global memory and passing in a
pointer to it. But arguments to kernels get stored in faster memory
than global memory don't they?
Right. You can pack a struct into a string using Python's struct module, and
On Freitag 18 Dezember 2009, Dan Piponi wrote:
go.prepare(s, ...) # tell PyCuda we're passing in a string buffer
go.prepared_call(grid, struct.pack(i,12345))# pack integer into
string buffer
struct_typestr = i
sz = struct.calcsize(struct_typestr)
go.prepare(%ds % sz, ...) # tell PyCuda
On Montag 21 Dezember 2009, Ewan Maxwell wrote:
test_driver.py works(all 16 tests), the example code i mentioned works to
however, other tests still fail with the same reason(nvcc fatal~)
That's strange. If all of them have the same path, why would some fail and
some succeed?
Andreas
On Montag 21 Dezember 2009, oli...@olivernowak.com wrote:
like i said.
a week.
Can you comment on what made this difficult? Can we do anything to make this
easier, e.g. by catching common errors and providing more helpful messages?
Andreas
signature.asc
Description: This is a digitally
On Dienstag 22 Dezember 2009, Justin Riley wrote:
Hi All,
I've added a page for installing PyCuda on Gentoo Linux to the PyCuda wiki.
Sweet, thanks!
Andreas
signature.asc
Description: This is a digitally signed message part.
___
PyCUDA mailing
Couple points:
* bytewise smem write may be slow?
* sync before and after timed operation, otherwise you time who knows what
* or, even better, use events.
HTH,
Andreas
On Samstag 02 Januar 2010, Hampton G. Miller wrote:
I have noticed something which seems odd and which I hope you will look
n Mittwoch 06 Januar 2010, Ying Wai (Daniel) Fan wrote:
Now in your situation there's a failure when reactivating the context to
detach from it, probably because the runtime is meddling about. The only
reason why cuCtxPushCurrent would throw an invalid value, is, IMO, if
that context is
On Donnerstag 07 Januar 2010, Ying Wai (Daniel) Fan wrote:
I changed cuComplex_mod.h a bit to force the use of complex.h. Looks
like the route of using GNU C library does not work. Complex arithmetic
operations are regarded as host functions by CUDA and host functions
cannot be called from
On Donnerstag 07 Januar 2010, Ian Ozsvald wrote:
I'm having a devil of a time getting pyCUDA to work on my MacBook and I
can't get past this error:
host47:examples ian$ python demo.py
Traceback (most recent call last):
File demo.py, line 22, in module
)
File
On Donnerstag 07 Januar 2010, Nicholas S-A wrote:
Well, if somebody writes code that uses arch=sm_13 for some reason,
then somebody who doesn't have a 200 series card tries to use it, then
the error message which comes up is pretty cryptic. Just trying to make
it more understandable. It is an
1 - 100 of 159 matches
Mail list logo
