Re: [pypy-dev] Vectorizing numpy traces

2015-03-01 Thread Vincent Legoll
I coincidentally read something related yesterday, it's not completely on topic, but was an interesting bit of info about firefox OS JIT and the use of fork() to amortize some costs. You can start reading at : http://www.realworldtech.com/forum/?threadid=146598&curpostid=147184 That's a digressio

Re: [pypy-dev] Vectorizing numpy traces

2015-02-28 Thread Armin Rigo
Hi Bengt, On 25 February 2015 at 15:20, Bengt Richter wrote: > Maybe it's worth a re-think, if only to say "no, we really mean no" in the > FAQ ;-) It's unclear to me if you're suggesting something more than adding a checkpointing system to stop and restart the process. It's a hack that might w

Re: [pypy-dev] Vectorizing numpy traces

2015-02-25 Thread Bengt Richter
Hi Vincent, I was aware of the FAQ item (my similar question long ago may have helped put it in the FAQ ;-) AIUI the main issue is re-establishing the memory mapping, which I think could be re-established by mmap-ing the saved files, if those files were created through mmap in the first place (

Re: [pypy-dev] Vectorizing numpy traces

2015-02-25 Thread Maciej Fijalkowski
On Wed, Feb 25, 2015 at 11:28 AM, Richard Plangger wrote: > Thx for your response. > > Yes I would be interested in a rewritten loop. > > After browsing the jittracer longer I found the following. > > ``` > label(p0, f16, p2, p3, p55, i54, i59, p20, i18, p6, i24, p36, i34, i40, > f32, i15, i23, i3

Re: [pypy-dev] Vectorizing numpy traces

2015-02-24 Thread Vincent Legoll
Hello Bengt, If I'm not mistaken I think this FAQ item should at least partly answer your question : http://pypy.readthedocs.org/en/latest/faq.html#couldn-t-the-jit-dump-and-reload-already-compiled-machine-code Regards On Wed, Feb 25, 2015 at 1:12 AM, Bengt Richter wrote: > On 02/24/2015 11:1

Re: [pypy-dev] Vectorizing numpy traces

2015-02-24 Thread Bengt Richter
On 02/24/2015 11:17 PM Maciej Fijalkowski wrote: Hi Richard. I will respond inline On Tue, Feb 24, 2015 at 8:18 PM, Richard Plangger wrote: hi, [...] (1) Is there a better way to get loops hot? no, not really (you can lower the threshold though, see pypy --jit help for details, only glo

Re: [pypy-dev] Vectorizing numpy traces

2015-02-24 Thread Maciej Fijalkowski
Hi Richard. I will respond inline On Tue, Feb 24, 2015 at 8:18 PM, Richard Plangger wrote: > hi, > > i'm currently trying to find a way to generate simd code for python > loops that operate on numpy arrays. > The IRC is quite busy so I think I'd rather post it as an email... > > I have familiar

Re: [pypy-dev] Vectorizing numpy traces

2015-02-24 Thread Laura Creighton
The PyPy core developers are at a sprint in Leysin right now, and they happen to be out for dinner right now. So you, alas, are likely to need to wait. Sorry for impatience Laura ___ pypy-dev mailing list pypy-dev@python.org https://mail.python.or

Re: [pypy-dev] Vectorizing numpy traces

2015-02-24 Thread Maciej Fijalkowski
before I answer, any clue why I get: Google Chrome's connection attempt to postimg.org was rejected. The website may be down, or your network may not be properly configured. On Tue, Feb 24, 2015 at 8:18 PM, Richard Plangger wrote: > hi, > > i'm currently trying to find a way to generate simd cod