Re: [pypy-dev] JITing non looping interpreted functions

2014-09-29 Thread Armin Rigo
Hi Alex, On 29 September 2014 01:31, Alex Gaynor wrote: > So, one solution is to simply write this loop in the interpreted language > (this is what I did for Topaz, methods such as Array#each are just some ruby > code). An alternative is to make a JitDriver for that function, see can see > this p

Re: [pypy-dev] JITing non looping interpreted functions

2014-09-28 Thread Alex Gaynor
So, one solution is to simply write this loop in the interpreted language (this is what I did for Topaz, methods such as Array#each are just some ruby code). An alternative is to make a JitDriver for that function, see can see this pattern in pypy/objspace/std/setobject.py Alex On Sun, Sep 28, 20

[pypy-dev] JITing non looping interpreted functions

2014-09-28 Thread Timothy Baldridge
Let's say I have a bit of interpreter level code code that does something as simple as reduce: acc = None for x in range(1): acc = interpret(func, wrap(x)) return acc The problem I seem to be hitting is that since there isn't a loop inside the code (in the func variable) interpret is runn