Re: [pypy-dev] An idea about automatic parallelization in PyPy/RPython

2014-11-26 Thread haael
first, just abort the optimized run. If the loop turns out to be parralelizable, return the results instead. Thanks haael Od: "黄若塵" Do: "Armin Rigo" ; ha...@interia.pl; Wysłane: 9:07 Środa 2014-11-26 Temat: Re: [pypy-dev] An idea about automatic parallelization in P

Re: [pypy-dev] An idea about automatic parallelization in PyPy/RPython

2014-11-21 Thread Armin Rigo
Hi Haael, hi 黄若尘, On 21 November 2014 10:55, wrote: > I would suggest a different approach, more similar to Armin's idea of > parallelization. > > You could just optimistically assume that the loop is parallelizable. Just > execute few steps at once (each in its own memory sandbox) and check f

Re: [pypy-dev] An idea about automatic parallelization in PyPy/RPython

2014-11-21 Thread haael
eers haael Od: "黄若尘" Do: "Maciej Fijalkowski" ; Wysłane: 7:49 Piątek 2014-11-21 Temat: Re: [pypy-dev] An idea about automatic parallelization in PyPy/RPython > Yes, I actually knew this way to get traces. > > Well, what I mean is that, I want to handle those

Re: [pypy-dev] An idea about automatic parallelization in PyPy/RPython

2014-11-20 Thread 黄若尘
Yes, I actually knew this way to get traces. Well, what I mean is that, I want to handle those traces in RUNTIME. I want to insert some code in RPython’s JIT to detect some traces which can be executed parallel, if so, then COMPILE them into OpenCL code (then into native code, and run), if not,

Re: [pypy-dev] An idea about automatic parallelization in PyPy/RPython

2014-11-20 Thread Maciej Fijalkowski
You get traces by running PYPYLOG=jit-log-opt,jit-backend: pypy There is a tool call jitviewer for viewing those traces. OpenCL is likely just written in C and the kernel itself does not contain any Python. On Fri, Nov 21, 2014 at 3:17 AM, 黄若尘 wrote: > Hi Fijaklowski, > > Thank you very muc

Re: [pypy-dev] An idea about automatic parallelization in PyPy/RPython

2014-11-20 Thread 黄若尘
Hi Fijaklowski, Thank you very much for your reply. Yes, you are right, it’s too hard for me to implement automatic parallelization for the whole PyPy’s trace JIT. I think maybe I can firstly do some work with a very simple interpreter (for example the example-interpreter introduced by PyPy do

Re: [pypy-dev] An idea about automatic parallelization in PyPy/RPython

2014-11-20 Thread Maciej Fijalkowski
Hi 黄若尘 This is generally a hard problem that projects like GCC or LLVM didn't get very far. The problem is slightly more advanced with PyPys JIT, but not much more. However, the problem is you can do it for simple loops, but the applications are limited outside of pure numerics (e.g. numpy) and a

Re: [pypy-dev] An idea about automatic parallelization in PyPy/RPython

2014-11-19 Thread haael
Hi I find it brilliant. Thanks haael Od: "黄若尘" Do: pypy-dev@python.org; Wysłane: 2:46 Wtorek 2014-11-18 Temat: [pypy-dev] An idea about automatic parallelization in PyPy/RPython > Hi everyone, > >I’m a master student in Japan and I want to do some research

[pypy-dev] An idea about automatic parallelization in PyPy/RPython

2014-11-17 Thread 黄若尘
Hi everyone, I’m a master student in Japan and I want to do some research in PyPy/RPython. I have read some papers about PyPy and I also had some ideas about it. I have communicated with Mr. Bloz and been advised to send my question here. Actually, I wonder if it is possible to ma