Mailman 3 July 2013 - pypy-dev

Translating pypy on FreeBSD with CLI backend
by David Naylor July 28, 2013

July 28, 2013

Hi, I tried to translate pypy-2.0b2 on FreeBSD-9.1/i386 and I get the following error: [Timer] Timings: [Timer] annotate --- 218.3 s [Timer] rtype_ootype --- 137.0 s [Timer] ========================================== [Timer] Total: --- 355.4 s [translation:ERROR] Error: [translation:ERROR] Traceback (most recent call last): [translation:ERROR] File "/tmp/tmp/pypy/work/pypy-pypy-4b60269153b5/rpython/translator/goal/translate.py", line 317, in main [translation:ERROR] drv.proceed(goals) [translation:ERROR] File "/tmp/tmp/pypy/work/pypy-pypy-4b60269153b5/rpython/translator/driver.py", line 733, in proceed [translation:ERROR] return self._execute(goals, task_skip = self._maybe_skip()) [translation:ERROR] File "/tmp/tmp/pypy/work/pypy-pypy-4b60269153b5/rpython/translator/tool/taskengine.py", line 114, in _execute [translation:ERROR] res = self._do(goal, taskcallable, *args, **kwds) [translation:ERROR] File "/tmp/tmp/pypy/work/pypy-pypy-4b60269153b5/rpython/translator/driver.py", line 284, in _do [translation:ERROR] res = func() [translation:ERROR] File "/tmp/tmp/pypy/work/pypy-pypy-4b60269153b5/rpython/translator/driver.py", line 360, in task_rtype_ootype [translation:ERROR] rtyper.specialize(dont_simplify_again=True) [translation:ERROR] File "/tmp/tmp/pypy/work/pypy-pypy-4b60269153b5/rpython/rtyper/rtyper.py", line 207, in specialize [translation:ERROR] self.specialize_more_blocks() [translation:ERROR] File "/tmp/tmp/pypy/work/pypy-pypy-4b60269153b5/rpython/rtyper/rtyper.py", line 250, in specialize_more_blocks [translation:ERROR] self.specialize_block(block) [translation:ERROR] File "/tmp/tmp/pypy/work/pypy-pypy-4b60269153b5/rpython/rtyper/rtyper.py", line 404, in specialize_block [translation:ERROR] self.gottypererror(e, block, hop.spaceop, newops) [translation:ERROR] File "/tmp/tmp/pypy/work/pypy-pypy-4b60269153b5/rpython/rtyper/rtyper.py", line 402, in specialize_block [translation:ERROR] self.translate_hl_to_ll(hop, varmapping) [translation:ERROR] File "/tmp/tmp/pypy/work/pypy-pypy-4b60269153b5/rpython/rtyper/rtyper.py", line 531, in translate_hl_to_ll [translation:ERROR] resultvar = hop.dispatch() [translation:ERROR] File "/tmp/tmp/pypy/work/pypy-pypy-4b60269153b5/rpython/rtyper/rtyper.py", line 759, in dispatch [translation:ERROR] return translate_meth(self) [translation:ERROR] File "<17296-codegen /tmp/tmp/pypy/work/pypy-pypy-4b60269153b5/rpython/rtyper/rtyper.py:611>", line 5, in translate_op_is_ [translation:ERROR] return pair(r_arg1, r_arg2).rtype_is_(hop) [translation:ERROR] File "/tmp/tmp/pypy/work/pypy-pypy-4b60269153b5/rpython/rtyper/rmodel.py", line 293, in rtype_is_ [translation:ERROR] return hop.rtyper.type_system.generic_is(robj1, robj2, hop) [translation:ERROR] File "/tmp/tmp/pypy/work/pypy-pypy-4b60269153b5/rpython/rtyper/typesystem.py", line 179, in generic_is [translation:ERROR] roriginal1, roriginal2)) [translation:ERROR] TyperError: is of instances of the non-instances: <OOErasedRepr Object>, <OOErasedRepr Object> [translation:ERROR] .. (pypy.objspace.std.setobject:517)IntegerSetStrategy._difference_update_unwrapped [translation:ERROR] .. block@3 with 2 exits(v961) [translation:ERROR] .. v964 = is_(v962, v963) Is the CLI supported in general, on FreeBSD or broken? Regards

9 15

GPS tracker with multi discrete与您共享了相册。
by GPS tracker with multi discrete July 25, 2013

July 25, 2013

Tips: GPS tracker with multi discrete input and output /Attn: purchase manager Dear Sir This is Anna,the sales manager of Redview GPS in China. VT310 is a GPS tracker with 5 discrete inputs ,5 discrete outputs and 2 analog ports . With VT310,you can get vehicle windows status, door status, engine status, temperature and tank fuel level ,etc. This is widely used in truck tracking application. I would appreciate if you forward this letter to Technical Manager or to other expert responsible for technical integration of new products in your company, or provide me with his contact for we could discuss all the details of our future cooperation. Your early reply is highly appreciated. Best Regards Anna https://picasaweb.google.com/lh/sredir?uname=110555139617906055901&target=A…

1 0

asmgcc assertion error in lang-smalltalk
by Lars Wassermann July 20, 2013

July 20, 2013

Hello, in the project lang-smalltalk, we have a problem we don't know where exactly the source may be. When running the VM with jit, we get: PyPy assertion failed at rpython_memory_gctransform_asmgcroot.c:583: in pypy_g_locate_caller_based_on_retaddr: found a stack frame that does not belong anywhere I know, bug in asmgcc Aborted (core dumped) When running without jit, everything works fine. Is the fact that the error only occurs when using the JIT a hint that the bug may not be in asmgcc? The code to interact with plugins which where compiled as dynamic libraries for the original Smalltalk VM is there [1]. When loading a plugin, it is initialized supplying a (named) function list, which is created around line 978. Can anybody see an obvious mistake we did when using the llhelper? (The llhelper-arguments are recorded in line 104.) Thank you, Lars [1] https://bitbucket.org/pypy/lang-smalltalk/src/8f27fbc5ff8c38b44be7ccbfa060c…

3 5

Re: [pypy-dev] pypy-dev Digest, Vol 27, Issue 14
by Kunal Puri July 20, 2013

July 20, 2013

Well i would love to meet you so do let me know. I came home this evening amidst heavy rain and all. The weather here just seems to get worse each year. Was on my way back when i read the news. Your provine or not. I think its terrible when circumstances push you to such an extreme to do such a thing. 105 days! Wow. Thats a long time. I hope it isnt much longer now. Love you babe..and ill speak to you on mon... On Jul 20, 2013 3:32 PM, <pypy-dev-request(a)python.org> wrote: > Send pypy-dev mailing list submissions to > pypy-dev(a)python.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.python.org/mailman/listinfo/pypy-dev > or, via email, send a message with subject or body 'help' to > pypy-dev-request(a)python.org > > You can reach the person managing the list at > pypy-dev-owner(a)python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of pypy-dev digest..." > > > Today's Topics: > > 1. Re: asmgcc assertion error in lang-smalltalk (Lars Wassermann) > 2. Re: asmgcc assertion error in lang-smalltalk (Carl Friedrich Bolz) > 3. Announcement: PyPy London Sprint (August 26 - September 1 > 2013) (Carl Friedrich Bolz) > 4. Re: asmgcc assertion error in lang-smalltalk (Armin Rigo) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 19 Jul 2013 12:28:40 +0200 > From: Lars Wassermann <lars.wassermann(a)student.hpi.uni-potsdam.de> > To: <pypy-dev(a)python.org> > Subject: Re: [pypy-dev] asmgcc assertion error in lang-smalltalk > Message-ID: <51E914D8.8050205(a)student.hpi.uni-potsdam.de> > Content-Type: text/plain; charset="ISO-8859-1" > > On 07/19/2013 11:51 AM, Carl Friedrich Bolz wrote: > > On 19/07/13 11:36, Lars Wassermann wrote: > >> Hello, > >> in the project lang-smalltalk, we have a problem we don't know where > >> exactly the source may be. > >> When running the VM with jit, we get: > >> > >> PyPy assertion failed at rpython_memory_gctransform_asmgcroot.c:583: > >> in pypy_g_locate_caller_based_on_retaddr: found a stack frame that does > >> not belong anywhere I know, bug in asmgcc > >> Aborted (core dumped) > >> > >> When running without jit, everything works fine. > >> > >> Is the fact that the error only occurs when using the JIT a hint that > >> the bug may not be in asmgcc? > > > > You can try to see whether it goes away when not using asmgcc, by > > translating with: > > > > rpython --gcrootfinder=shadowstack -Ojit ...target... > > > > Cheers, > > > > Carl Friedrich > > _______________________________________________ > > pypy-dev mailing list > > pypy-dev(a)python.org > > http://mail.python.org/mailman/listinfo/pypy-dev > > > That fixed the problem. Is there a way to generate a bug report for > asmgcc, or would that be too complicated? > > Thank you, > Lars > > > ------------------------------ > > Message: 2 > Date: Fri, 19 Jul 2013 12:44:39 +0200 > From: Carl Friedrich Bolz <cfbolz(a)gmx.de> > To: pypy-dev(a)python.org > Subject: Re: [pypy-dev] asmgcc assertion error in lang-smalltalk > Message-ID: <51E91897.3080402(a)gmx.de> > Content-Type: text/plain; charset=ISO-8859-1 > > On 19/07/13 12:28, Lars Wassermann wrote: > > On 07/19/2013 11:51 AM, Carl Friedrich Bolz wrote: > >> You can try to see whether it goes away when not using asmgcc, by > >> translating with: > >> > >> rpython --gcrootfinder=shadowstack -Ojit ...target... > > > > That fixed the problem. Is there a way to generate a bug report for > > asmgcc, or would that be too complicated? > > What do you mean? You can add one to bugs.pypy.org (asmgcc is part of > PyPy). > > Cheers, > > Carl Friedrich > > > > ------------------------------ > > Message: 3 > Date: Fri, 19 Jul 2013 15:47:35 +0200 > From: Carl Friedrich Bolz <cfbolz(a)gmx.de> > To: pypy-dev(a)python.org > Subject: [pypy-dev] Announcement: PyPy London Sprint (August 26 - > September 1 2013) > Message-ID: <51E94377.2060006(a)gmx.de> > Content-Type: text/plain; charset=ISO-8859-1 > > ===================================================================== > PyPy London Sprint (August 26 - September 1 2013) > ===================================================================== > > The next PyPy sprint will be in London, United Kingdom for the first > time. This is a fully public sprint. PyPy sprints are a very good way > to get into PyPy development and no prior PyPy knowledge is necessary. > > > ------------------------------ > Goals and topics of the sprint > ------------------------------ > > For newcomers: > > * bring your application/library and we'll help you port it to PyPy, > benchmark and profile > > * come and write your favorite missing numpy function > > * help us work on developer tools like jitviewer > > We'll also work on: > > * refactoring the JIT optimizations > > * STM and STM-related topics > > * anything else attendees are interested in > > ----------- > Exact times > ----------- > > The work days should be August 26 - September 1 2013 (Monday-Sunday). > The official plans are for people to arrive on the 26th, and > to leave on the 2nd. There will be a break day in the middle. > We'll typically start at 10:00 in the morning. > > > ------------ > Location > ------------ > > The sprint will happen within a room of `King's College's`_ `Strand > Campus`_ in `Central London, UK`_. There are some travel instructions > `how to > get there`_. We are being hosted by `Laurence Tratt`_ and the `Software > Development Team`_. > > .. _`King's College's`: http://www.kcl.ac.uk/ > .. _`Central London, UK`: http://goo.gl/maps/Qz0zz > .. _`Strand Campus`: > http://www.kcl.ac.uk/campuslife/campuses/strand/StrandCampusLocation.aspx > .. _`how to get there`: > http://www.kcl.ac.uk/campuslife/campuses/directions/strand.aspx > .. _`Laurence Tratt`: http://tratt.net/laurie > .. _`Software Development Team`: http://soft-dev.org > > ------------ > Demo Session > ------------ > > If you don't want to come to the full sprint, but still want to chat a > bit, we are planning to have a demo session on Tuesday August 27. We > will announce this separately on the blog. If you are interested, please > leave a comment. > > -------------- > Registration > -------------- > > If you want to attend, please register by adding yourself to the > "people.txt" file in Mercurial:: > > https://bitbucket.org/pypy/extradoc/ > https://bitbucket.org/pypy/extradoc/raw/extradoc/sprintinfo/london-2013 > > or on the pypy-dev mailing list if you do not yet have check-in rights:: > > http://mail.python.org/mailman/listinfo/pypy-dev > > Remember that you may need a (insert country here)-to-UK power adapter. > Please note that UK is not within the Schengen zone, so non-EU and > non-Switzerland citizens may require specific visa. Please check `travel > regulations`_. Also, the UK uses pound sterling (GBP). > > .. _`travel regulations`: > http://www.ukba.homeoffice.gov.uk/visas-immigration/do-you-need-a-visa/ > > > ------------------------------ > > Message: 4 > Date: Sat, 20 Jul 2013 09:32:31 +0200 > From: Armin Rigo <arigo(a)tunes.org> > To: Lars Wassermann <lars.wassermann(a)student.hpi.uni-potsdam.de> > Cc: PyPy Developer Mailing List <pypy-dev(a)python.org> > Subject: Re: [pypy-dev] asmgcc assertion error in lang-smalltalk > Message-ID: > <CAMSv6X1j8xomZjLLE9JZKT+9h65hrCH= > xwvU+KStJOxL88ja3Q(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi Lars, > > On Fri, Jul 19, 2013 at 11:36 AM, Lars Wassermann > <lars.wassermann(a)student.hpi.uni-potsdam.de> > PyPy assertion failed > at rpython_memory_gctransform_asmgcroot.c:583: > > in pypy_g_locate_caller_based_on_retaddr: found a stack frame that does > > not belong anywhere I know, bug in asmgcc > > The best report for us would be to include exactly on which precise OS > this occurs, with which exact version of GCC, and the exact source > code (url and revision number); and the example that crashes. Then we > hope that the bug is really reproducible, which might not be the case. > > You can also try to give us the binary, and we attempt to run it. > > Failing that, you need to debug yourself the crash, which I can > explain how to do (but is not trivial). > > > A bient?t, > > Armin. > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > pypy-dev mailing list > pypy-dev(a)python.org > http://mail.python.org/mailman/listinfo/pypy-dev > > > ------------------------------ > > End of pypy-dev Digest, Vol 27, Issue 14 > **************************************** >

1 0

Announcement: PyPy London Sprint (August 26 - September 1 2013)
by Carl Friedrich Bolz July 19, 2013

July 19, 2013

===================================================================== PyPy London Sprint (August 26 - September 1 2013) ===================================================================== The next PyPy sprint will be in London, United Kingdom for the first time. This is a fully public sprint. PyPy sprints are a very good way to get into PyPy development and no prior PyPy knowledge is necessary. ------------------------------ Goals and topics of the sprint ------------------------------ For newcomers: * bring your application/library and we'll help you port it to PyPy, benchmark and profile * come and write your favorite missing numpy function * help us work on developer tools like jitviewer We'll also work on: * refactoring the JIT optimizations * STM and STM-related topics * anything else attendees are interested in ----------- Exact times ----------- The work days should be August 26 - September 1 2013 (Monday-Sunday). The official plans are for people to arrive on the 26th, and to leave on the 2nd. There will be a break day in the middle. We'll typically start at 10:00 in the morning. ------------ Location ------------ The sprint will happen within a room of `King's College's`_ `Strand Campus`_ in `Central London, UK`_. There are some travel instructions `how to get there`_. We are being hosted by `Laurence Tratt`_ and the `Software Development Team`_. .. _`King's College's`: http://www.kcl.ac.uk/ .. _`Central London, UK`: http://goo.gl/maps/Qz0zz .. _`Strand Campus`: http://www.kcl.ac.uk/campuslife/campuses/strand/StrandCampusLocation.aspx .. _`how to get there`: http://www.kcl.ac.uk/campuslife/campuses/directions/strand.aspx .. _`Laurence Tratt`: http://tratt.net/laurie .. _`Software Development Team`: http://soft-dev.org ------------ Demo Session ------------ If you don't want to come to the full sprint, but still want to chat a bit, we are planning to have a demo session on Tuesday August 27. We will announce this separately on the blog. If you are interested, please leave a comment. -------------- Registration -------------- If you want to attend, please register by adding yourself to the "people.txt" file in Mercurial:: https://bitbucket.org/pypy/extradoc/ https://bitbucket.org/pypy/extradoc/raw/extradoc/sprintinfo/london-2013 or on the pypy-dev mailing list if you do not yet have check-in rights:: http://mail.python.org/mailman/listinfo/pypy-dev Remember that you may need a (insert country here)-to-UK power adapter. Please note that UK is not within the Schengen zone, so non-EU and non-Switzerland citizens may require specific visa. Please check `travel regulations`_. Also, the UK uses pound sterling (GBP). .. _`travel regulations`: http://www.ukba.homeoffice.gov.uk/visas-immigration/do-you-need-a-visa/

1 0

Pypy translation fails on MIPS (without JIT)
by Alexis BRENON July 18, 2013

July 18, 2013

Hi everyone, As someones know, I'm working for a company (as an internship) on the MIPS port of Pypy. I started the JIT backend but not finished and for the moment I try to translate Pypy without JIT (because JIT isn't finished). I try to translate it directly on the target, even if it will take very very long time. But for the moment I only try to compile a small Rpython snippet : def main(args): print "Hello World" return 0 def target(*args): return main, None with this command line : python ../../rpython/bin/rpython -O1 test.py Then, I've got this translation configuration : [translation] translate.py configuration: [translation] [translate] [translation] opt = 1 [translation] targetspec = test [translation] translation configuration: [translation] [translation] [translation] [backendopt] [translation] inline_threshold = 16.2 [translation] continuation = False [translation] gc = boehm [translation] gcremovetypeptr = False [translation] gcrootfinder = n/a [translation] gctransformer = boehm [translation] list_comprehension_operations = True Annotating&Simplifying is OK, as RTyping, backend optimisations, stack checking, database creation and C generation. But during compilation, the first instruction fails... [platform:execute] make -j 2 in /tmp/usession-unknown-12/testing_1 [platform:Error] /opt/cross-native-mipsel-linux-gnu/bin/../lib/gcc/mipsel-linux-gnu/4.4.6/../../../../mipsel-linux-gnu/bin/ld: test-c: local symbol `__data_start' in /opt/cross-native-mipsel-linux-gnu/bin/../mipsel-linux-gnu/sysroot/usr/lib/crt1.o is referenced by DSO [platform:Error] /opt/cross-native-mipsel-linux-gnu/bin/../lib/gcc/mipsel-linux-gnu/4.4.6/../../../../mipsel-linux-gnu/bin/ld: final link failed: Bad value [platform:Error] collect2: ld returned 1 exit status [platform:Error] make: *** [test-c] Error 1 I search on Google and all I found is that it can comes from binutils 2.21, I try to create a new toolchain with binutils 2.22 but same error... Is anyone got any idea where I can search to debug this ? Thanks, Alexis

6 17

PyPy doesn't make code written in C faster
by Armin Rigo July 18, 2013

July 18, 2013

Hi all, Some people learn about PyPy, and the first program they try to measure speed with is something like this: def factorial(n): res = 1 for i in range(1, n + 1): res *= i return res print factorial(25000) It may not be completely obvious a priori, but this is as bogus as it gets. This is by now only 50% slower in PyPy than in CPython thanks to efforts from various people. The issue is of course that it's an algo which, in CPython or in PyPy, spends most of its time in C code computing with rather large "long" objects. (No, PyPy doesn't contain magic to speed up C code 10 times.) In fact, this program spends more than 2/3rd of its time in the final repr() of the result! Converting a long to base 10 is a quadratic operation. Does it still make sense to add programs like this to our benchmarks? So far, our benchmarks are "real-life" examples. The benchmarks like above are completely missing the point of PyPy, as they don't stress at all the Python interpreter part. There are also other cases where PyPy's performance is very bad, like cpyext on an extension module with lots of small C API calls. I believe that it would still make sense to list such cases in the official benchmark, and have the descriptions of the benchmarks explain what's wrong with them. A bientôt, Armin.

6 13

ndarray-subtype branch looking for review
by Matti Picus July 17, 2013

July 17, 2013

The ndarray-branch passes tests both translated and untranslated. I ran it through the numpy test suite as well, specifically the matrix class tests, and it seems to pass them. Would anyone like to review, or should I just go ahead and merge? Specifically, I may have missed some w_ prefixes on app-level instances, or may not have tested all the code paths, and I had to hack the FakeSpace in compile.py to allow subclassing. Matti

3 5

PyPy 2.1 beta released
by Maciej Fijalkowski July 11, 2013

July 11, 2013

=============== PyPy 2.1 beta 1 =============== We're pleased to announce the first beta of the upcoming 2.1 release of PyPy. This beta contains many bugfixes and improvements, numerous improvements to the numpy in PyPy effort. The main feature being that the ARM processor support is not longer considered alpha level. We would like to thank the Raspberry PiFoundation (http://www.raspberrypi.org) for supporting the work to finish PyPy's ARM support. You can download the PyPy 2.1 beta 1 release here: http://pypy.org/download.html Highlights ========== * Bugfixes to the ARM JIT backend, so that ARM is now an officially supported processor architecture * Stacklet support on ARM * Interpreter improvements * Various numpy improvements * Bugfixes to cffi and ctypes * Bugfixes to the stacklet support * Improved logging performance * Faster sets for objects What is PyPy? ============= PyPy is a very compliant Python interpreter, almost a drop-in replacement for CPython 2.7.3. It's fast due to its integrated tracing JIT compiler. This release supports x86 machines running Linux 32/64, Mac OS X 64 or Windows 32. Also this release supports ARM machines running Linux 32bit - anything with ``ARMv6`` (like the Raspberry Pi) or ``ARMv7`` that supports ``VFPv3`` should work. Cheers, the PyPy team

1 0

PyPy 2.1 beta 1 released
by David Schneider July 11, 2013

July 11, 2013

=============== PyPy 2.1 beta 1 =============== We're pleased to announce the first beta of the upcoming 2.1 release of PyPy. This beta contains many bugfixes and improvements, numerous improvements to the numpy in PyPy effort. The main feature being that the ARM processor support is not longer considered alpha level. We would like to thank the Raspberry PiFoundation (http://www.raspberrypi.org) for supporting the work to finish PyPy's ARM support. You can download the PyPy 2.1 beta 1 release here: http://pypy.org/download.html Highlights ========== * Bugfixes to the ARM JIT backend, so that ARM is now an officially supported processor architecture * Stacklet support on ARM * Interpreter improvements * Various numpy improvements * Bugfixes to cffi and ctypes * Bugfixes to the stacklet support * Improved logging performance * Faster sets for objects What is PyPy? ============= PyPy is a very compliant Python interpreter, almost a drop-in replacement for CPython 2.7.3. It's fast due to its integrated tracing JIT compiler. This release supports x86 machines running Linux 32/64, Mac OS X 64 or Windows 32. Also this release supports ARM machines running Linux 32bit - anything with ``ARMv6`` (like the Raspberry Pi) or ``ARMv7`` that supports ``VFPv3`` should work. Cheers, the PyPy team

1 0