Mailman 3 July 2010 - pypy-dev

PyPy Proxy
by Hart's Antler 27 Jul '10

27 Jul '10

The code from PyPyGTK has been generalized so that it can work with PyGame, and PyODE. Function calls are improved so that different arg types can be accepted by defining custom wrappers per function. Custom wrappers can also be made for the return values, so different types can be handled as well (it seems that rpython restricts what can be returned from a function to the same types). Proxy objects can move back and forth from CPython to RPython. The wrappers for pygtk, pyode, and pygame are by no means complete, but some basic tests are working. Callbacks are limited to quoted lambdas, but it could be improved. http://pastebin.com/rWEfgMSN I had seen the other proxy method before, but found few examples, how does it work, from Rpython or the PyPy interpreter? http://morepypy.blogspot.com/2009/11/using-cpython-extension-modules-with.h…

2 2

PyPyGTK v0.1
by Hart's Antler 24 Jul '10

24 Jul '10

http://pastebin.com/UhnEurqb The above is a crude way to run pygtk from rpython (through CPython and talking on a pipe), but at least it partially works. Callbacks are limited to quoted lambdas, but some simple return types back to rpython is possible - i'm going to try that next. There is no support for dynamic attribute access, but most of pygtk involves function calls. Where attribute access is required, i guess extra proxy functions could be written. -brett

2 1

rpython questions, **kw, __call__, __getattr__
by Hart's Antler 23 Jul '10

23 Jul '10

Looking through the pypy source code i see **kw, __call__ and __getattr__ are used, but when i try to write my own rpython code that uses these conventions, i get translation errors. Do i need to borrow from "application space" in order to do this or can i just give hints to the annotator? Thanks, -brett #this is allowed def func(*args): print(args) #but this is not? def func(**kw): print(args) #error call pattern too complex #this class fails to translate, are we not allowed to define our own __call__ and __getattr__ in rpython? class A(object): __call__(*args): print(args) __getattr__(self,name): print(name)

3 2

Building a shared library on x86-64 fails due to static linking of libffi
by Jason Creighton 22 Jul '10

22 Jul '10

Hello, While working on asmgcc-64, I ran into this issue. For some reason, PyPy wants to link libffi statically on some platforms, Linux included. But when compiling with the "shared" option (as is done in some asmgcroot tests), you get link errors like: /usr/bin/ld: /usr/lib/libffi.a(ffi64.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC /usr/lib/libffi.a: could not read symbols: Bad value I interpret this to mean that since we building a shared library, the resulting library must be position independent, so we can't link in non-PIC such as is found in the static version of libffi on my system. (Ubuntu 10.04, x86-64). And indeed, if I switch to linking dynamically, the error goes away and things seem to work. However, I don't want to just blindly enable dynamic linking, because there must be a reason it was configured to link statically in the first place. What is that reason? Also, what steps should I take here? I think I need to enable dynamic linking of libffi on x86-64 Linux when building a shared library at the very least, but to reduce the number of code paths, I'm somewhat inclined to link dynamically whether we're building a library or not. What do you guys think? Thanks, Jason

3 2

Re: [pypy-dev] [pypy-svn] r76268 - pypy/branch/micronumpy/pypy/tool
by Maciej Fijalkowski 19 Jul '10

19 Jul '10

Benchmarks generally should go to pypy/benchmarks directory in the main source tree (that is svn+ssh://codespeak.net/svn/pypy/benchmarks) On Sat, Jul 17, 2010 at 12:41 AM, <dan(a)codespeak.net> wrote: > Author: dan > Date: Sat Jul 17 00:41:02 2010 > New Revision: 76268 > > Added: > pypy/branch/micronumpy/pypy/tool/convolve.py > Modified: > pypy/branch/micronumpy/pypy/tool/numpybench.py > Log: > Oops, I forgot the most important part of the benchmark! > > Added: pypy/branch/micronumpy/pypy/tool/convolve.py > ============================================================================== > --- (empty file) > +++ pypy/branch/micronumpy/pypy/tool/convolve.py Sat Jul 17 00:41:02 2010 > @@ -0,0 +1,43 @@ > +from __future__ import division > +from __main__ import numpy as np > + > +def naive_convolve(f, g): > + # f is an image and is indexed by (v, w) > + # g is a filter kernel and is indexed by (s, t), > + # it needs odd dimensions > + # h is the output image and is indexed by (x, y), > + # it is not cropped > + if g.shape[0] % 2 != 1 or g.shape[1] % 2 != 1: > + raise ValueError("Only odd dimensions on filter supported") > + # smid and tmid are number of pixels between the center pixel > + # and the edge, ie for a 5x5 filter they will be 2. > + # > + # The output size is calculated by adding smid, tmid to each > + # side of the dimensions of the input image. > + vmax = f.shape[0] > + wmax = f.shape[1] > + smax = g.shape[0] > + tmax = g.shape[1] > + smid = smax // 2 > + tmid = tmax // 2 > + xmax = vmax + 2*smid > + ymax = wmax + 2*tmid > + # Allocate result image. > + h = np.zeros([xmax, ymax], dtype=f.dtype) > + # Do convolution > + for x in range(xmax): > + for y in range(ymax): > + # Calculate pixel value for h at (x,y). Sum one component > + # for each pixel (s, t) of the filter g. > + s_from = max(smid - x, -smid) > + s_to = min((xmax - x) - smid, smid + 1) > + t_from = max(tmid - y, -tmid) > + t_to = min((ymax - y) - tmid, tmid + 1) > + value = 0 > + for s in range(s_from, s_to): > + for t in range(t_from, t_to): > + v = x - smid + s > + w = y - tmid + t > + value += g[smid - s, tmid - t] * f[v, w] > + h[x, y] = value > + return h > > Modified: pypy/branch/micronumpy/pypy/tool/numpybench.py > ============================================================================== > --- pypy/branch/micronumpy/pypy/tool/numpybench.py (original) > +++ pypy/branch/micronumpy/pypy/tool/numpybench.py Sat Jul 17 00:41:02 2010 > @@ -21,13 +21,29 @@ > return numpy.array(kernel) > > if __name__ == '__main__': > - from sys import argv as args > - width, height, kwidth, kheight = [int(x) for x in args[1:]] > + from optparse import OptionParser > + > + option_parser = OptionParser() > + option_parser.add_option('--kernel-size', dest='kernel', default='3x3', > + help="The size of the convolution kernel, given as WxH. ie 3x3" > + "Note that both dimensions must be odd.") > + option_parser.add_option('--image-size', dest='image', default='256x256', > + help="The size of the image, given as WxH. ie. 256x256") > + option_parser.add_option('--runs', '--count', dest='count', default=1000, > + help="The number of times to run the convolution filter") > + > + options, args = option_parser.parse_args() > + > + def parse_dimension(arg): > + return [int(s.strip()) for s in arg.split('x')] > + > + width, height = parse_dimension(options.image) > + kwidth, kheight = parse_dimension(options.kernel) > + count = int(options.count) > > image = generate_image(width, height) > kernel = generate_kernel(kwidth, kheight) > > from timeit import Timer > convolve_timer = Timer('naive_convolve(image, kernel)', 'from convolve import naive_convolve; from __main__ import image, kernel; gc.enable()') > - count = 100 > print "%.5f sec/pass" % (convolve_timer.timeit(number=count)/count) > _______________________________________________ > pypy-svn mailing list > pypy-svn(a)codespeak.net > http://codespeak.net/mailman/listinfo/pypy-svn >

1 0

Windows binaries
by Dave Cross 13 Jul '10

13 Jul '10

Hi, Is there a likely delivery date for Windows binaries of PyPy 1.3? Dave. </PRE> ********************************************************************** Please consider the environment - do you really need to print this email? This email is intended only for the person(s) named above and may contain private and confidential information. If it has come to you in error, please destroy and permanently delete any copy in your possession and contact us on +44 (0) 161 480 4420. The information in this email is copyright © CDL Group Holdings Limited. We cannot accept any liability for any loss or damage sustained as a result of software viruses. It is your responsibility to carry out such virus checking as is necessary before opening any attachment. Cheshire Datasystems Limited uses software which automatically screens incoming emails for inappropriate content and attachments. If the software identifies such content or attachment, the email will be forwarded to our Technology Department for checking. You should be aware that any email which you send to Cheshire Datasystems Limited is subject to this procedure. Cheshire Datasystems Limited, Strata House, Kings Reach Road, Stockport SK4 2HD Registered in England and Wales with Company Number 3991057 VAT registration: 727 1188 33 <PRE>

2 1

Interactive Translation and JIT
by Hart's Antler 09 Jul '10

09 Jul '10

I'm using Jason Creighton branch, and i am trying to test the JIT from interactive translation. Is it now allowed? I'm getting this error: NotImplementedError: --gcrootfinder=asmgcc requires standalone Or am i not setting the options correctly on the translator, here is how i'm translating. from pypy.translator.interactive import Translation t = Translation( pypy_entry_point ) t.config.translation.suggest(jit=True, jit_debug='steps', jit_backend='x86', gc='boehm') t.annotate() t.rtype() f = t.compile_c() f() complete code: http://pastebin.com/T42cqSbz demo: http://www.youtube.com/watch?v=HwbDG3Rdi_Q -brett

2 2

Re: [pypy-dev] [pypy-svn] r75824 - in pypy/branch/interplevel-array/pypy/module/array: . test
by Hakan Ardo 05 Jul '10

05 Jul '10

I've checked in a dict-based version. Not sure it became that clean after all. Is the getattr(space, tc.unwrap) construction ok? On Mon, Jul 5, 2010 at 7:26 AM, Hakan Ardo <Hakan(a)ardoe.net> wrote: > On Sun, Jul 4, 2010 at 10:25 PM, Maciej Fijalkowski <fijall(a)gmail.com> wrote: >> >> Hey. This looks a bit ugly, > > It does, doesn't it :) > >> you can definitely do it with some >> constant dict or something > > Yes, there is an overflow check needed on the integer types but not on > the character an float types, but I guess that could be solved with a > flag in the dict. > > I was actually considering to introduce separate subclasses for each > typecode overriding intem_w and descr_getitem. That would get rid of > the typecode attribute lookup all together. > >> (we have special support for iterating over >> constants and unrolling the iteration, look for unrolling_iterable). >> Also, annotator can fold a bunch of ifs into a switch, but not if "in" >> operator is used (or is fine though). > > That's nice features, good to know about. Thanx. > > > > -- > Håkan Ardö > -- Håkan Ardö

1 0

Re: [pypy-dev] [pypy-svn] r75824 - in pypy/branch/interplevel-array/pypy/module/array: . test
by Hakan Ardo 05 Jul '10

05 Jul '10

On Sun, Jul 4, 2010 at 10:25 PM, Maciej Fijalkowski <fijall(a)gmail.com> wrote: > > Hey. This looks a bit ugly, It does, doesn't it :) > you can definitely do it with some > constant dict or something Yes, there is an overflow check needed on the integer types but not on the character an float types, but I guess that could be solved with a flag in the dict. I was actually considering to introduce separate subclasses for each typecode overriding intem_w and descr_getitem. That would get rid of the typecode attribute lookup all together. > (we have special support for iterating over > constants and unrolling the iteration, look for unrolling_iterable). > Also, annotator can fold a bunch of ifs into a switch, but not if "in" > operator is used (or is fine though). That's nice features, good to know about. Thanx. -- Håkan Ardö

1 0

Re: [pypy-dev] [pypy-svn] r75824 - in pypy/branch/interplevel-array/pypy/module/array: . test
by Maciej Fijalkowski 05 Jul '10

05 Jul '10

> + > + def item_w(self, w_item): > + space=self.space > + if self.typecode == 'c': > + return self.space.str_w(w_item) > + elif self.typecode == 'u': > + return self.space.unicode_w(w_item) > + > + elif self.typecode == 'b': > + item=self.space.int_w(w_item) > + if item<-128: > + msg='signed char is less than minimum' > + raise OperationError(space.w_OverflowError, space.wrap(msg)) > + elif item>127: > + msg='signed char is greater than maximum' > + raise OperationError(space.w_OverflowError, space.wrap(msg)) > + return rffi.cast(rffi.SIGNEDCHAR, item) > + elif self.typecode == 'B': > + item=self.space.int_w(w_item) > + if item<0: > + msg='unsigned byte integer is less than minimum' > + raise OperationError(space.w_OverflowError, space.wrap(msg)) > + elif item>255: > + msg='unsigned byte integer is greater than maximum' > + raise OperationError(space.w_OverflowError, space.wrap(msg)) > + return rffi.cast(rffi.UCHAR, item) > + > + elif self.typecode == 'h': > + item=self.space.int_w(w_item) > + if item<-32768: > + msg='signed short integer is less than minimum' > + raise OperationError(space.w_OverflowError, space.wrap(msg)) > + elif item>32767: > + msg='signed short integer is greater than maximum' > + raise OperationError(space.w_OverflowError, space.wrap(msg)) > + return rffi.cast(rffi.SHORT, item) > + elif self.typecode == 'H': > + item=self.space.int_w(w_item) > + if item<0: > + msg='unsigned short integer is less than minimum' > + raise OperationError(space.w_OverflowError, space.wrap(msg)) > + elif item>65535: > + msg='unsigned short integer is greater than maximum' > + raise OperationError(space.w_OverflowError, space.wrap(msg)) > + return rffi.cast(rffi.USHORT, item) > + > + elif self.typecode in ('i', 'l'): > + item=self.space.int_w(w_item) > + if item<-2147483648: > + msg='signed integer is less than minimum' > + raise OperationError(space.w_OverflowError, space.wrap(msg)) > + elif item>2147483647: > + msg='signed integer is greater than maximum' > + raise OperationError(space.w_OverflowError, space.wrap(msg)) > + return rffi.cast(lltype.Signed, item) > + elif self.typecode in ('I', 'L'): > + item=self.space.int_w(w_item) > + if item<0: > + msg='unsigned integer is less than minimum' > + raise OperationError(space.w_OverflowError, space.wrap(msg)) > + elif item>4294967295: > + msg='unsigned integer is greater than maximum' > + raise OperationError(space.w_OverflowError, space.wrap(msg)) > + return rffi.cast(lltype.Unsigned, item) > + > + elif self.typecode == 'f': > + item=self.space.float_w(w_item) > + return rffi.cast(lltype.SingleFloat, item) > + elif self.typecode == 'd': > + return self.space.float_w(w_item) > + Hey. This looks a bit ugly, you can definitely do it with some constant dict or something (we have special support for iterating over constants and unrolling the iteration, look for unrolling_iterable). Also, annotator can fold a bunch of ifs into a switch, but not if "in" operator is used (or is fine though).

1 0