Hi Art, Min, Bryan,
On Mon, 20 Sep 2010 15:25:24 -0700, Art wrote:
> Thanks for posting the fork. I used your modification to compiler.py (my
> original one was incorrect) and I built a 64-bit only version of pycuda and
> all tests under tests/ passed for the first time. I also was able to call
>
On Mon, Sep 20, 2010 at 2:08 PM, MinRK wrote:
> Okay, with a tiny tweak to compiler.compile, I have UB pycuda working in
> both 64 and 32-bit. All I did was tell compile() to add '-m64' to options
> if it detects 64-bit mode, in the same way as Bryan's trick.
>
> I pushed a branch with the patch
Okay, with a tiny tweak to compiler.compile, I have UB pycuda working in
both 64 and 32-bit. All I did was tell compile() to add '-m64' to options
if it detects 64-bit mode, in the same way as Bryan's trick.
I pushed a branch with the patch to my GitHub:
http://github.com/minrk/pycuda, as well as
On Fri, 17 Sep 2010 14:54:11 -0400, Yiyin Zhou wrote:
> Hi,
> I was trying to pass some complex valued numbers to a kernel, but somehow it
> messed up. Here is an example with GPUArray that can be reproduced on several
> of our linux servers:
>
> initialize...
>
> import pycuda.gpuarray as gpu
Hi Nicolas,
On Mon, 20 Sep 2010 18:21:28 +0200, Nicolas Barbey
wrote:
> Thanks for this great package which ease so much the use of cuda !
> I think I found out a small bug in the current git version of the code.
> If you run the following code in ipython :
>
> >>> from pycuda import autoinit
>
On Mon, Sep 20, 2010 at 8:34 AM, Bryan Catanzaro wrote:
> I think it should be changed to check to see if the Python interpreter is
> currently running in 32 bit mode, and then compile to match:
>
> if 'darwin' in sys.platform and sys.maxint == 2147483647:
># The Python interpreter is running
Thanks Andreas -
Yes, unfortunately the patterns does change (the code I run grows and shrinks
mountain glaciers) so I think I'm out of luck with GPU processing here. I'll
consider some other options. Pycuda, nevertheless, is a great package - thanks
everyone for your hard work developing and
Bryan,
Note that in 3.2, all files in cuda/lib are UB, including cudart (finally!).
I build fat-binary on OS-X (up to date 10.6.4, cuda 3.2, etc.), simply by
setting the usual arch flags in siteconf.py:
CXXFLAGS = ["-arch", "x86_64", "-arch", "i386"]
LDFLAGS = ["-arch", "x86_64", "-arch", "i386"
Hello all,
Thanks for this great package which ease so much the use of cuda !
I think I found out a small bug in the current git version of the code.
If you run the following code in ipython :
>>> from pycuda import autoinit
>>> from pycuda import driver, compiler, gpuarray, tools
>>> a = gpuarra
I think it should be changed to check to see if the Python interpreter is
currently running in 32 bit mode, and then compile to match:
if 'darwin' in sys.platform and sys.maxint == 2147483647:
# The Python interpreter is running in 32 bit mode on OS X
if "-arch" not in conf["CXXFLAGS"]:
Of course, the most recent Mac Pros now ship with ATI.
http://www.apple.com/macpro/features/graphics.html
On Sun, Sep 19, 2010 at 9:24 PM, gerald wrong wrote:
> I think PyCUDA should attempt to build correctly as 64bit so once the
> python64 bugs are shaken out, PyCUDA will be able to build on M
11 matches
Mail list logo
