[pypy-dev] gpgpu and pypy

[Jeff Anderson-Lee]

  On 8/20/2010 2:18 PM, Maciej Fijalkowski wrote:
> On Fri, Aug 20, 2010 at 11:05 PM, Jeff Anderson-Lee
> <jonah at eecs.berkeley.edu>  wrote:
>>   On 8/20/2010 1:51 PM, Maciej Fijalkowski wrote:
>>> 2010/8/20 Paolo Giarrusso<p.giarrusso at gmail.com>:
>>>> 2010/8/20 Jorge Timón<timon.elviejo at gmail.com>:
>>>>> Hi, I'm just curious about the feasibility of running python code in a gpu
>>>>> by extending pypy.
>>>> Disclaimer: I am not a PyPy developer, even if I've been following the
>>>> project with interest. Nor am I an expert of GPU - I provide links to
>>>> the literature I've read.
>>>> Yet, I believe that such an attempt is unlikely to be interesting.
>>>> Quoting Wikipedia's synthesis:
>>>> "Unlike CPUs however, GPUs have a parallel throughput architecture
>>>> that emphasizes executing many concurrent threads slowly, rather than
>>>> executing a single thread very fast."
>>>> And significant optimizations are needed anyway to get performance for
>>>> GPU code (and if you don't need the last bit of performance, why
>>>> bother with a GPU?), so I think that the need to use a C-like language
>>>> is the smallest problem.
>>>>
>>>>> I don't have the time (and probably the knowledge neither) to develop that
>>>>> pypy extension, but I just want to know if it's possible.
>>>>> I'm interested in languages like openCL and nvidia's CUDA because I think
>>>>> the future of supercomputing is going to be GPGPU.
>>> Python is a very different language than CUDA or openCL, hence it's
>>> not completely to map python's semantics to something that will make
>>> sense for GPU.
>> Try googling: copperhead cuda
>> Also look at:
>>
>> http://code.google.com/p/copperhead/wiki/Installing
>>
> What's the point of posting here project which has not released any code?
1) He is packaging it up for release this month:
> Comment by bryan.catanzaro 
> <http://code.google.com/u/bryan.catanzaro/>, Aug 05, 2010
>
> Before the end of August. I'm working on packaging it up right now. =)
>
2) Bryan's got a good head on his shoulders and has been working on this 
problem or some time. Rather than (or at least before) starting off in a 
completely new direction, its worth looking at something that has been 
in the works for a while now and is attaining some maturity.
3) You are welcome to ignore it, but some folks might be interested, and 
at least they now know it is there and where to look for more 
information and forthcoming code.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20100820/308786dd/attachment.html>