Re: [pypy-dev] bug with MinGW32

2012-05-24 Thread bookaa
yes, it should be like this. thank you Bookaa From: Amaury Forgeot d'Arc Sent: Wednesday, May 23, 2012 9:26 PM To: bookaa Cc: pypy-dev@python.org Subject: Re: [pypy-dev] bug with MinGW32 2012/5/23 bookaa if platform.platform.cc.startswith('mingw32'): This is better written as: from

Re: [pypy-dev] Translating just the parser for JVM [was: Faster PyPy translation (for debugging)]

2012-05-24 Thread Philip Jenvey
On May 24, 2012, at 10:08 AM, Antonio Cuni wrote: > Hello Michal, > > On 05/24/2012 06:31 PM, Michal Bendowski wrote: >> Just two add my two cents: I made the JVM backend translate the >> standard interpreter in the jvm-improvements branch a few months ago >> (just a few changes). The branch has

[pypy-dev] +Site Place/ Analysis/ Offer

2012-05-24 Thread Ralph Dinkins
pypy-...@codespeak.net: Your site has a good look and feel but you're not getting as much web traffic as you could be getting. Can we show you how to change that? It won't cost you anything for us to review your online business and the results could spike your web revenue. Reply to us t

Re: [pypy-dev] Jit hints from python

2012-05-24 Thread Timothy Baldridge
> Note that already nowadays you can hack (maybe we should just make > such hacks more explicit): if you use not a general-purpose dictionary > but instead a namespace like a module or a class, then reads are > constant-folded with an out-of-line guard.  This means you could > rewrite your code for

Re: [pypy-dev] Jit hints from python

2012-05-24 Thread Armin Rigo
Hi Timothy, On Wed, May 23, 2012 at 2:44 PM, Timothy Baldridge wrote: > So my question is, how easy/hard would it be to somehow get a > @purefunction decorator in Python instead of just RPython? For that > matter, having __immutable_fields__ would also be nice, but that may > be asking for too mu

Re: [pypy-dev] Translating just the parser for JVM [was: Faster PyPy translation (for debugging)]

2012-05-24 Thread Antonio Cuni
Hello Michal, On 05/24/2012 06:31 PM, Michal Bendowski wrote: > Just two add my two cents: I made the JVM backend translate the > standard interpreter in the jvm-improvements branch a few months ago > (just a few changes). The branch has been closed though and I had a > busy time so I didn't do an

Re: [pypy-dev] Translating just the parser for JVM [was: Faster PyPy translation (for debugging)]

2012-05-24 Thread Maciej Fijalkowski
On Thu, May 24, 2012 at 6:19 PM, Timothy Baldridge wrote: > > I've been meaning to dip a toe in PyPy but had trouble getting the JVM > > translator to work the last time I tried. How hard would it be to use > > a fake space (or some other technique) to just spit out a parser for > > the JVM? > > >

Re: [pypy-dev] Translating just the parser for JVM [was: Faster PyPy translation (for debugging)]

2012-05-24 Thread fwierzbi...@gmail.com
On Thu, May 24, 2012 at 9:31 AM, Michal Bendowski wrote: > Just two add my two cents: I made the JVM backend translate the > standard interpreter in the jvm-improvements branch a few months ago > (just a few changes). The branch has been closed though and I had a > busy time so I didn't do anythin

Re: [pypy-dev] Translating just the parser for JVM [was: Faster PyPy translation (for debugging)]

2012-05-24 Thread Michal Bendowski
Just two add my two cents: I made the JVM backend translate the standard interpreter in the jvm-improvements branch a few months ago (just a few changes). The branch has been closed though and I had a busy time so I didn't do anything about it. For the last few weeks/months I was sitting in my cav

Re: [pypy-dev] Translating just the parser for JVM [was: Faster PyPy translation (for debugging)]

2012-05-24 Thread fwierzbi...@gmail.com
On Thu, May 24, 2012 at 9:19 AM, Timothy Baldridge wrote: > Side note, I would really love to see the JVM backend more maintained. > If I could write Clojure in RPython, then run it on the JVM...with a > full tracing JIT, that would just be insanely awesome. Holy turtles all the way down batman!

Re: [pypy-dev] Translating just the parser for JVM [was: Faster PyPy translation (for debugging)]

2012-05-24 Thread Timothy Baldridge
> I've been meaning to dip a toe in PyPy but had trouble getting the JVM > translator to work the last time I tried. How hard would it be to use > a fake space (or some other technique) to just spit out a parser for > the JVM? Side note, I would really love to see the JVM backend more maintained.

[pypy-dev] Translating just the parser for JVM [was: Faster PyPy translation (for debugging)]

2012-05-24 Thread fwierzbi...@gmail.com
On Thu, May 24, 2012 at 7:24 AM, wrote: > if it can find the errors, then the fastest is to use: > >   pypy/bin/checkmodule.py > > but I very rarely find errors that way. Second is to write a jit test, > which does partial translation (only of the code reachable from the test) > and can use a f

Re: [pypy-dev] Faster PyPy translation (for debugging)

2012-05-24 Thread wlavrijsen
Hi Timothy, On my machine that takes about 800sec before it starts rtyping my module. Are there some better options I can use if I simply want to make sure that my module will fit into the PyPy typesystem? if it can find the errors, then the fastest is to use: pypy/bin/checkmodule.py but

Re: [pypy-dev] Faster PyPy translation (for debugging)

2012-05-24 Thread Amaury Forgeot d'Arc
Hi, 2012/5/24 Timothy Baldridge > pypy translate.py --opt=0 targetpypystandalone.py > > On my machine that takes about 800sec before it starts rtyping my > module. Are there some better options I can use if I simply want to > make sure that my module will fit into the PyPy typesystem? > I often

[pypy-dev] Faster PyPy translation (for debugging)

2012-05-24 Thread Timothy Baldridge
I'm working on writing a module for PyPy, the code runs fine via py.py, but I'm still debugging the RTyping errors. What can I do to speed up the translation process. Currently I'm running pypy translate.py --opt=0 targetpypystandalone.py On my machine that takes about 800sec before it starts rt