Mailman 3 September 2005 - pypy-dev

Very long compilation on pypy
by Arthur Peters Sept. 7, 2005

Sept. 7, 2005

I successfully compiled pypy a couple days ago. Then I took the source file and tried to compile it with optimizations. That didn't go as well. It's been compiling for the last 2 days (process time is 2098minutes at the moment) and has not finished. The command line was: gcc -O2 -c testing_1.c -o testing_1.o -I/usr/include/python2.4 \ -I ~/source/pypy-dist/pypy/translator/c/ -I /usr/include/gc/ I just aborted it because it was making the system slow. Has anyone else experienced this? Does -O2 trigger a bug in GCC with the large source file? or does it really take 3-4 days to compile it? Just thought I'd bring it up. I'm using the braohm GC. -Arthur

4 5

Re: [pypy-svn] r17215 - pypy/dist/pypy/rpython
by hpk＠trillke.net Sept. 7, 2005

Sept. 7, 2005

Hi Christian, hi all, On Mon, Sep 05, 2005 at 02:32 +0200, tismer(a)codespeak.net wrote: > Modified: pypy/dist/pypy/rpython/rlist.py > ============================================================================== > --- pypy/dist/pypy/rpython/rlist.py (original) > +++ pypy/dist/pypy/rpython/rlist.py Mon Sep 5 02:32:49 2005 > @@ -393,8 +393,10 @@ > _ll_list_resize(l, length+1) > i = length > items = l.items > + i1 = i+1 > while i > 0: > - items[i] = items[i+1] > + items[i] = items[i1] > + i1 = i > i -= 1 > items[0] = newitem this and this ... > @@ -403,8 +405,10 @@ > _ll_list_resize(l, length+1) > items = l.items > i = length > + i1 = i+1 > while i > index: > - items[i] = items[i+1] > + items[i] = items[i1] > + i1 = i > i -= 1 > items[i] = newitem ... are such optimizations measurably effective at all? I would think that such low-level details are handled by the backend or, if not, that we could write a generic transformation that does that for us. Or am i missing something? cheers, holger

2 1

[hatcliff@cis.ksu.edu: [PEPM 2006] Call For Papers]
by Armin Rigo Sept. 6, 2005

Sept. 6, 2005

Hi, A conference where I'd probably like to go, early 2006: ----- Forwarded message from John Hatcliff <hatcliff(a)cis.ksu.edu> ----- Date: Wed, 27 Jul 2005 16:53:01 -0500 From: John Hatcliff <hatcliff(a)cis.ksu.edu> To: arigo(a)tunes.org Subject: [PEPM 2006] Call For Papers Reply-To: hatcliff(a)cis.ksu.edu Hi Armin, I wanted to send you a personal email to encourage you to consider submitting a paper and attending PEPM 2006 -- to held in conjunction with POPL 2006 in Charleston, South Carolina (USA) on January 9-10, 2006. As an author of a PEPM 2004 paper, I am sure that you are interested in seeing PEPM continue as a successful meeting in which researchers interested in a variety of forms of semantics-based program manipulation meet to present results and exchange ideas that drive future research. Frank Tip and I, serving as program co-chairs for PEPM 2006, are working hard to put together a strong and diverse program committee and workshop format that we hope will lead to an exciting meeting. We've included the PEPM 2006 Call For Papers below and you can find additional information on the PEPM web-page (http://www.cis.ksu.edu/santos/pepm06). As you can see from the CFP and the program committee we are aiming to continue to broaden PEPM to consider a variety of forms of semantics-based program manipulation including refactoring, rule-based transformations, slicing, model-driven code generation and transformations. In closing, Frank and I would like to encourage you again to considering submitting to PEPM 2006 and to help us in our publicity efforts by forwarding the PEPM CFP below to any colleagues who might be interested in PEPM 2006. If you have any questions about suitable topics/content for PEPM submissions, please do not hesitate to email the PC Chairs directly. Best regards, john ==================================================================== C A L L F O R P A P E R S === P E P M 2006 === ACM SIGPLAN 2006 Workshop on Partial Evaluation and Program Manipulation (Affiliated with POPL 2006) http://www.cis.ksu.edu/santos/pepm06 January 9-10, 2006 Charleston, South Carolina The PEPM Symposium/Workshop series aims to bring together researchers and practitioners working in the areas of program manipulation, partial evaluation, and program generation. PEPM focuses on techniques, supporting theory, tools, and applications of the analysis and manipulation of programs. The 2006 PEPM workshop will be based on a broad interpretation of semantics-based program manipulation. This year, a concerted effort will be made to expand the scope of PEPM significantly beyond the traditionally covered areas of partial evaluation and specialization and include practical applications of program transformations such as refactoring tools, and practical implementation techniques such as rule-based transformation systems. In addition, the scope of PEPM will be broadened to cover manipulation and transformations of program and system representations such as structural and semantic models that occur in the context of model-driven development. In order to reach out to practitioners, a separate category of tool demonstration papers will be solicited. Topics of interest for PEPM'06 include, but are not limited to: * Program and model manipulation techniques such as transformations driven by rules, patterns, or analyses, partial evaluation, specialization, slicing, symbolic execution, refactoring, aspect weaving, decompilation, and obfuscation. * Program analysis techniques that are used to drive program/model manipulation such as abstract interpretation, static analysis, binding-time analysis, dynamic analysis, constraint solving, and type systems. * Analysis and transformation for programs/models with advanced features such as objects, generics, ownership types, aspects, reflection, XML type systems, component frameworks, and middleware. * Techniques that treat programs/models as data objects including meta-programming, generative programming, model-driven program generation and transformation. * Application of the above techniques including experimental studies, engineering needed for scalability, and benchmarking in a wide variety of domains including source code manipulation, domain-specific language implementations, scientific computing, middleware frameworks and infrastructure needed for distributed and web-based applications. We especially encourage papers that break new ground including descriptions of how program/model manipulation tools can be integrated into realistic software development processes, descriptions of robust tools capable of effectively handling realistic applications, and new areas of application such as rapidly evolving systems, distributed and web-based programming including middleware manipulation, model-driven development, and on-the-fly program adaptation driven by run-time or statistical analysis. Submission Categories, Guidelines, and Proceedings: Regular Research Papers must not exceed 10 pages in ACM Proceedings style. Tool demonstration papers must not exceed 4 pages in ACM Proceedings style, and authors will be expected to present a live demonstration of the described tool at the workshop. Suggested topics, evaluation criteria, and writing guidelines for both research tool demonstration papers will be made available on the PEPM'06 Web-site. Papers should be submitted electronically via the workshop web site. We plan to publish the workshop proceedings in ACM SIGPLAN Notices (with full papers appearing in the ACM Digital Library) and selected papers will be invited for a journal special issue dedicated to PEPM'06. Important Dates: Submission........: October 7, 2005 Apia, 11:59pm, Samoan time (firm deadline, no extensions) Notification......: November 18, 2005 Camera-Ready Paper: December 16, 2005. Workshop co-Chairs: John Hatcliff, Kansas State University, USA (hatcliff(a)cis.ksu.edu) Frank Tip, IBM T.J. Watson Research Center, USA (ftip(a)us.ibm.com) PEPM 2006 Program Committee: Krzysztof Czarnecki University of Waterloo Gary Daugherty Rockwell Collins Advanced Technology Center Tom Dean Queen's University Mangala Gowri Nanda IBM India John Hatcliff (co-chair) Kansas State University Nevin Heintze Agere Systems Jaakko J?rvi Texas A & M University Jens Krinke University of Hagen Shriram Krishnamurthi Brown University Julia Lawall University of Copenhagen (DIKU) Oege de Moor Oxford University Germ?n Puebla Technical University of Madrid Peter Sestoft Royal Veterinary and Agricultural University (Denmark) Gregor Snelting University of Passau Frank Tip (co-chair) IBM T.J. Watson Research Center Eelco Visser Universiteit Utrecht -- ---------------------------------------------------------------------------- John Hatcliff Phone: 785-532-6350 Professor Fax..: 785-532-7353 Department of Computing and Information Sciences Email: hatcliff(a)cis.ksu.edu 234 Nichols Hall WWW..: http://www.cis.ksu.edu/~hatcliff Kansas State University Manhattan, KS 66506 ---------------------------------------------------------------------------- ----- End forwarded message -----

1 0

ANN: PyPy Sprint in Paris October 10th to 16th
by Ludovic Aubry Sept. 5, 2005

Sept. 5, 2005

Here is the official sprint announcement You can also find it here : http://codespeak.net/pypy/extradoc/sprintinfo/paris-2005-sprint.html PyPy Sprint in Paris 10th - 16th October 2005 ========================================================== The next PyPy sprint will take place in Paris at Logilab's office in France from the 10th to the 16th of October 2005 (both days fully included). To learn more about the new PyPy Python implementation look here: http://codespeak.net/pypy Goals and topics of the sprint ------------------------------ Now that pypy-0.7.0_ has been released, it is time for refactoring and planning of the next features. For these reasons the currently scheduled main topics of this sprint will be: - threading and GC - refactoring and translation features - discussing/experimenting towards JIT_ and `continuation-passing`_ style translation Moreover, we are open to work in other areas that participants are interested in. Please raise topics on the mailinglist_. Location & Accomodation ------------------------ The sprint will be held in Logilab's offices in Paris. The exact address is:: 10 rue Louis Vicat 75015 Paris We'll provide WLAN connection and there is a small kitchen to make tea and coffee. `See here`_ for a map of the area nearby. There are two metro lines and three bus lines that stop close to Logilab's: - Metro line 12 : stop "Porte de Versailles" - Metro line 13 : stop "Malakoff plateau de Vanves" - Bus 89 or 58 : stop "Carrefour Albert Legris" - Bus PC1 : stop "Porte de la Plaine" Those are more or less within 5 minutes walk. There is a huge number of hotels_ in Paris, all of which are unfortunately rather expensive. Here is another site for `hotels en France`_. It should be no problem to reach the sprint venue from anywhere in Paris using public transportation. However it would be better to find accomodation in the southern districts (14th, 15th) or in the nearby towns (Malakoff, Vanves) not far from Paris. Another good choice is to find an hotel near one of the metro line above. (avoid long bus trips as it takes more time.) Looking at the map here: hotels_, the area you should look at is between (3) and (6), (5) is still ok. As an alternative you could also try to group (4 or 5 people) and try to rent a furnished appartment for the week. Almost all announces from French websites come from `Lodgis agency`_. They are rather expensive but most of the time it can be cheaper than hotels. For the more adventurous you can look on the french site pap_ which lists rental ads. (select appartements, dÃ©partement=75, arrondissements=15,14,13) For transportation we strongly recommend the public transportation (metro and buses). There are weekly tickets (monday to sunday) from 15.70 euros (Zone 1-2). You need a picture (ID format) and ask for a *Carte Orange*. Don't get the tourist's cards which are more expensive and valid only for 5 days. Also note that zone 1-2 won't pay for your ticket from the airport and is valid only (mostly) inside Paris. If you arrive by plane this will be most probably at Roissy airport and from there you can take the RER line B to Paris for about 8 euros. .. _`See here`: http://www.logilab.com/contact .. _hotels: http://www.hotel-paris.net/index-hotels-English.htm .. _`hotels en France`: http://www.0800paris-hotels.com/ .. _pap: http://www.pap.fr/immobilier/offres/offre-location-vacances.asp .. _`Lodgis agency`: http://www.lodgis.com/ Exact times ----------- The PyPy sprint is held Monday 10th October - Sunday 16th October 2005. Hours will be from 09:00 until 20:00. It's a good idea to arrive a day before the sprint starts and leave a day later. In the middle of the sprint there usually is a break day and it's usually ok to take half-days off if you feel like it. Network, Food ------------- There are plenty of restaurants and sandwich places around and a big supermarket for those who would rather make their own food. You will probably need a wireless network card to access the network but we can provide ethernet cables for those who don't have one. Registration etc. ----------------- Please subscribe to the `PyPy sprint mailing list`_, introduce yourself and post a note that you want to come. Feel free to ask any questions there! There also is a separate `Paris people`_ page tracking who is already thought to come. If you have commit rights on codespeak then you can modify yourself a checkout of http://codespeak.net/svn/pypy/extradoc/sprintinfo/paris-2005-people.txt .. _`Paris people`: http://codespeak.net/pypy/index.cgi?extradoc/sprintinfo/paris-people.html .. _`mailinglist`: .. _`PyPy sprint mailing list`: http://codespeak.net/mailman/listinfo/pypy-sprint .. _`pypy-0.7.0`: http://codespeak.net/pypy/dist/pypy/doc/release-0.7.0.html .. _JIT: http://en.wikipedia.org/wiki/Just-in-time_compilation .. _`continuation-passing`: http://en.wikipedia.org/wiki/Continuation_passing_style

1 0

Re: [pypy-svn] r17217 - pypy/dist/pypy/interpreter/astcompiler
by Ludovic Aubry Sept. 5, 2005

Sept. 5, 2005

Please make sure you modify astgen.py at the same time. ast.py is generated by astgen.py which is a modified version of the original CPython generator. On Mon, 2005-09-05 at 10:30 +0200, pedronis(a)codespeak.net wrote: > Author: pedronis > Date: Mon Sep 5 10:30:22 2005 > New Revision: 17217 > > Modified: > pypy/dist/pypy/interpreter/astcompiler/ast.py > Log: > some getChildNodes were still returning tuples > > > > Modified: pypy/dist/pypy/interpreter/astcompiler/ast.py > ============================================================================== > --- pypy/dist/pypy/interpreter/astcompiler/ast.py (original) > +++ pypy/dist/pypy/interpreter/astcompiler/ast.py Mon Sep 5 10:30:22 2005 > @@ -332,7 +332,7 @@ > return () > > def getChildNodes(self): > - return () > + return [] > > def __repr__(self): > return "Break()" > @@ -449,7 +449,7 @@ > return () > > def getChildNodes(self): > - return () > + return [] > > def __repr__(self): > return "Continue()" > @@ -538,7 +538,7 @@ > return () > > def getChildNodes(self): > - return () > + return [] > > def __repr__(self): > return "Ellipsis()" > @@ -1107,7 +1107,7 @@ > return () > > def getChildNodes(self): > - return () > + return [] > > def __repr__(self): > return "NoneConst()" > @@ -1176,7 +1176,7 @@ > return () > > def getChildNodes(self): > - return () > + return [] > > def __repr__(self): > return "Pass()" > _______________________________________________ > pypy-svn mailing list > pypy-svn(a)codespeak.net > http://codespeak.net/mailman/listinfo/pypy-svn

1 0

Release
by Ben.Young＠risk.sungard.com Sept. 5, 2005

Sept. 5, 2005

Congratulations everyone one the release! It looks really good! So what's the next priority? Speed or more customisability (or both!)? Cheers, Ben

7 9

refactoring Module discovery/implementation?
by hpk＠trillke.net Sept. 2, 2005

Sept. 2, 2005

Hi pypy-dev, I'd like to suggest heading towards making PyPy's mixed C-ported modules more self-contained and not have it's implementation and initilization spread over several directories and code areas. IMO it's good that CPython has basically one C file that describes a Module's implementation. With Python we could make it a package so that we can still separate information like interp-level, app-level and low-level glue code but keep things more together and have it picked up via some more plugin-based scheme. The package scheme (probably based on the current mixed modules approach) should have a runtime interface and try to stay indepedent from the inner PyPy developments like where exactly things at low level are located. With "runtime interface" i mean that PyPy would automatically discover all modules in a given plugin/module directory by importing and querying them to get information the provided module, a description (docstring) and e.g. which ll-functions are provided and special annotations and what not. Oh, and "py.py --listmodules" should provide a full view of available modules (and modules included by the current defaults) so that you can pass that to --usemodules="x,y,z". This involves a bit of API design that we haven't done much for our internal stuff yet but i think it's about time to provide some nicer APIs and separate things. What do you think? A sprint topic? First write documentation and then implement? cheers, holger

3 2

PyCON draft CFP has a proposed submission deadline of Oct 31.
by Laura Creighton Sept. 2, 2005

Sept. 2, 2005

Just so nobody is surprised. See: http://mail.python.org/mailman/private/pycon-organizers/2005-September/0041… Laura

3 3