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,
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
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
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
Hi,
On 19 November 2014 23:52, Philip Jenvey wrote:
> I'm still getting the expected discrepancy between the two: Exception raised
> on both pypy and pypy3, whereas __getitem__ isn’t called on CPython 2.7.5.
> You might want to double check your python binaries?
Indeed, issue 708 isn't "fixed"
