Mailman 3 March 2015 - pypy-dev

Codespeed as on speed.pypy.org
by Christian Peel 12 Mar '15

12 Mar '15

Hi all, I'm working with the author of Codespeed (Miquel Torres) to determine whether there would be interest in a hosted service which provided information similar to those from Codespeed as used at speed.pypy.org. Our belief is that pypy.org would be interested in using a freemium hosted service with features similar to (or better than!) those in codespeed and which was as easy to set up as Travis CI; can you confirm this? What additional features would you want in such a service? Are any of you using Codespeed commercially? My best Chris -- chris.peel(a)ieee.org

3 5

fdopen(fd, 'w') whe fd is opened 'r'
by Matti Picus 11 Mar '15

11 Mar '15

2 3

Re: [pypy-dev] [pypy-commit] pypy vmprof: uh
by Maciej Fijalkowski 09 Mar '15

09 Mar '15

uh, I really don't think this checkin is correct (it was meant to seek to the end, not 2 bytes) On Sun, Mar 8, 2015 at 7:03 PM, arigo <noreply(a)buildbot.pypy.org> wrote: > Author: Armin Rigo <arigo(a)tunes.org> > Branch: vmprof > Changeset: r76280:4c0fa46303da > Date: 2015-03-08 18:03 +0100 > http://bitbucket.org/pypy/pypy/changeset/4c0fa46303da/ > > Log: uh > > diff --git a/pypy/module/__pypy__/interp_magic.py b/pypy/module/__pypy__/interp_magic.py > --- a/pypy/module/__pypy__/interp_magic.py > +++ b/pypy/module/__pypy__/interp_magic.py > @@ -141,4 +141,4 @@ > try: > return space.wrap(ec.code_info_file.read()) > finally: > - ec.code_info_file.seek(2, 0) > + ec.code_info_file.seek(0, 2) > _______________________________________________ > pypy-commit mailing list > pypy-commit(a)python.org > https://mail.python.org/mailman/listinfo/pypy-commit

3 2

trsnslating pypy to another language besides C
by Joonas Liik 09 Mar '15

09 Mar '15

Hey If i wanted to translate PyPy in to another language.. Where would i start? What would be the absolute minimum i had to do to get it working? I cant run any C code.. at all (obscure sandboxed platform that only runs an obscure scripting language none of you has probably ever heard of) how much of a problem will this be? how to mitigate?

7 16

Re: [pypy-dev] random numbers
by Matti Picus 08 Mar '15

08 Mar '15

Floris is seems you sent the response to only me. The "right" behaviour is to not use jumpahead, which does not work well enough to be part of python 3.1 (note the use of "likely" in the docstring): ''' jumpahead(self, n) method of random.Random instance Change the internal state to one that is likely far away from the current state. This method will not be in Py3.x, so it is better to simply reseed. ''' The implementation changed for python 2.4, in changeset https://hg.python.org/cpython/rev/edd056c4a40d/ as part of the adaptations to the Mersenne Twister generator that replaced WichmannHill in python 2.3 I will try to make pypy return the same values as cpython, but you should consider reseeding for each thread instead Matti On 07/03/15 14:33, Floris van Manen wrote: > >> On 7 Mar 2015, at 13:28, matti picus <matti.picus(a)gmail.com >> <mailto:matti.picus@gmail.com>> wrote: >> >> What did you try that led you to suspect they are different? >> Matti > > yes indeed. > Using the jumpahead() fnction will lead to different results. > I don't now which are the correct ones... > > > import random > > random.seed(12345) > for i in xrange(10): > print random.random() > print > randomState = random.getstate() > for i in xrange(10): > random.setstate(randomState) > random.jumpahead(1) > randomState = random.getstate() > print random.random() > > > ''' > standard python: > > 0.416619872545 > 0.0101691694571 > 0.825206509254 > 0.2986398552 > 0.368411689488 > 0.193661349045 > 0.566008168729 > 0.161687823929 > 0.124266884284 > 0.43293626801 > > jumpahead() > 0.94861718596 > 0.466389725591 > 0.440309106388 > 0.756595610966 > 0.329954203719 > 0.207243180479 > 0.982769966933 > 0.856141036147 > 0.746277878413 > 0.304000958341 > > > pypy > > 0.416619872545 > 0.0101691694571 > 0.825206509254 > 0.2986398552 > 0.368411689488 > 0.193661349045 > 0.566008168729 > 0.161687823929 > 0.124266884284 > 0.43293626801 > > jumpahead() > 0.41362858709 > 0.482594587067 > 0.363386428038 > 0.0122210322735 > 0.218894401377 > 0.786381037234 > 0.535611315209 > 0.545681381301 > 0.0153701629836 > 0.136216130724 > ''' >

4 5

random numbers
by Floris van Manen 07 Mar '15

07 Mar '15

Are the random number generators from pypy and the standard python generating the exact same numbers from identical seeds? .F

2 1

GSoC 15 vectorizing traces
by Richard Plangger 03 Mar '15

03 Mar '15

hi, pypy participated in GSoC 14 and my thesis mentor had the idea that it would benefit if I apply to GSoC 15 for my thesis. I'm currently planning my thesis and I think the application would be very similar to what is required to GSoC 15. Do you think that it would be worth trying? Best, Richard

2 1

Vectorizing numpy traces
by Richard Plangger 01 Mar '15

01 Mar '15

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 familiarized myself with pypy and read most of the docs and read the code in the metainterp to understand how the traces are built. I translated pypy with --withmod-micronumpy enabled (installed numpy pypy fork in an virtual env) and gave the jitviewer a try. Here is a sample program that does not really make sense, but I think it would contain opportunity to generate SIMD instructions. ``` import numpy def invoke(): a = numpy.zeros(1024) b = numpy.zeros(1024) c = numpy.zeros(1024) # (2) for i in range(0,1024): c[i] = a[i] + b[i] # (3) c = a + b if __name__ == '__main__': i = 0 # (1) while i < 500: invoke() i += 1 ``` Here is the trace of invoke visible in jitviewer (uploaded to https://postimg.org/image/kbntluw55/full/). Here are some questions I have that would really help me to get going: (1) Is there a better way to get loops hot? (2) I cannot really figure out what all those trace/loop parameters are. obviously i can guess some but most of them do not really make sense to me. Am I missing some settings to be able to display more information for the trace? In addition to that I do not really see any chance to generate a simd loop for (2). Every array access is (arguably) guarded by an array index overflow and I think to skip that check would be invalid. (3) There is no trace generated for this instruction? Does this internally call a c function? (4) What in our opinion makes sense to vectorize with simd instructions? Could you provide some sample loops/code (ranging from simple to complex loops)? I would really appreciate any help and/or push into the right direction. Best, Richard

5 10