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 <psillymathh...@gmail.com> 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 Mac OS X > without special flags etc. > My understanding from multiple build attempts is that there is a bug in the > various Mac 64bit python implementations causing them to run in 32bit even > when forced 64; this should eventually get fixed (if it has not already). I > admit after many days of frustration, I have not tried to build on mac64 in > about 2 months; perhaps I will give it another go this week and report here > to the list. > The ability to devel on Macs is very useful, since newer macs include CUDA > capable hardware... and there are lots of scientists with macs... Judging by > the old queries on the mailing list, there are many people who have spent > time fiddling with PyCUDA on mac64... so there must be significant interest > in this feature. > On Sun, Sep 19, 2010 at 8:55 PM, Andreas Kloeckner <li...@informa.tiker.net> > wrote: >> >> On Thu, 16 Sep 2010 14:37:31 -0400, gerald wrong >> <psillymathh...@gmail.com> wrote: >> > Looking at PyCUDA setup.py, I found this: >> > >> > if 'darwin' in sys.platform: >> > # prevent from building ppc since cuda on OS X is not compiled >> > for >> > ppc >> > # also, default to 32-bit build, since there doesn't appear to >> > be a >> > # 64-bit CUDA on Mac yet. >> > if "-arch" not in conf["CXXFLAGS"]: >> > conf["CXXFLAGS"].extend(['-arch', 'i386', '-m32']) >> > if "-arch" not in conf["LDFLAGS"]: >> > conf["LDFLAGS"].extend(['-arch', 'i386', '-m32']) >> > >> > Since 64bit CUDA support on Mac OS X is a reality since at least >> > CUDA3.1, >> > this should be changed. I know there are other problems regarding 32/64 >> > python stopping 64bit mac users at the moment (including myself), but >> > since >> > changes are being made to the PyCUDA code to make it compatible with >> > CUDA3.2 >> > anyway... >> >> It looks like this should just be killed wholesale--right? Or is there >> anything more appropriate that it should be changed to? >> >> Andreas >> > > > _______________________________________________ > PyCUDA mailing list > PyCUDA@tiker.net > http://lists.tiker.net/listinfo/pycuda > > _______________________________________________ PyCUDA mailing list PyCUDA@tiker.net http://lists.tiker.net/listinfo/pycuda
