Re: [pypy-dev] CFP: IWTC 2011: First International Workshop on Trace Compilation

2011-06-06 Thread Maciej Fijalkowski
On Tue, Jun 7, 2011 at 7:58 AM, Hakan Ardo wrote: > Hi, > would it be a good idea to submit something about our unrolling > efforts here? I'd be happy to put in some typing work for that. > However I've never published in this field before so I would suggest a > joint effort where someone else tak

Re: [pypy-dev] Arrays in rpython

2011-06-06 Thread Maciej Fijalkowski
On Mon, Jun 6, 2011 at 8:54 PM, Timothy Baldridge wrote: >> In case you don't already know: in Python (and RPython), lists are >> implemented as >> resizeable arrays, i.e. they look more like a C++ std::vector and not >> a std::list. >> >> This said, IIRC RPython has special code for fixed-size li

Re: [pypy-dev] CFP: IWTC 2011: First International Workshop on Trace Compilation

2011-06-06 Thread Hakan Ardo
Hi, would it be a good idea to submit something about our unrolling efforts here? I'd be happy to put in some typing work for that. However I've never published in this field before so I would suggest a joint effort where someone else takes more responsibility for the structure of the paper. On Mo

[pypy-dev] [GSoC] CTypes backend for Cython aiming PyPy - Week 2

2011-06-06 Thread Romain Guillebert
Hi I summarized the second week of my Summer of Code project in this blog post: http://rguillebert.blogspot.com/2011/06/cython-backend-aiming-pypy-week-2.html Cheers Romain ___ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/lis

Re: [pypy-dev] [pypy-commit] pypy default: (arigo, bivab) implement longlong2float and float2longlong in a way that is more close to the C standard. On ARM/32bit this code was causing a reodering of i

2011-06-06 Thread Antonio Cuni
On 06/06/11 18:07, bivab wrote: > static double pypy__longlong2float(long long x) { > +int i; > +double dd; > char *p = (char*)&x; > -return *((double*)p); > +char *d = (char*)ⅆ > +for(i = 0; i < 8; i++) { > +d[i] = p[i]; > +} > +return dd; speaking of po

Re: [pypy-dev] Arrays in rpython

2011-06-06 Thread Timothy Baldridge
> In case you don't already know: in Python (and RPython), lists are > implemented as > resizeable arrays, i.e. they look more like a C++ std::vector and not > a std::list. > > This said, IIRC RPython has special code for fixed-size lists. > I think you just have to avoid all resizing functions. >

Re: [pypy-dev] Arrays in rpython

2011-06-06 Thread Amaury Forgeot d'Arc
Hi, 2011/6/6 Timothy Baldridge : > Is there a way in rpython to specify that a given list should be > implemented as an array? I want to create a list of objects exactly 32 > entries long. I could use [] but it seems like that would be slower > than using an array. In CPython I can create an array

Re: [pypy-dev] Compiling PyPy 1.5 fails on Slackware 13.37

2011-06-06 Thread Armin Rigo
Hi, The problem should be fixed now (017e187b2716). Can you try again? Hopefully I didn't break Windows or Mac builds, but I cannot easily be sure. Feel free to blame me if I did :-) A bientôt, Armin. ___ pypy-dev mailing list pypy-dev@python.org h

[pypy-dev] Arrays in rpython

2011-06-06 Thread Timothy Baldridge
Is there a way in rpython to specify that a given list should be implemented as an array? I want to create a list of objects exactly 32 entries long. I could use [] but it seems like that would be slower than using an array. In CPython I can create an array of primitive types, but I'm looking to cr

[pypy-dev] CFP: IWTC 2011: First International Workshop on Trace Compilation

2011-06-06 Thread Carl Friedrich Bolz
IWTC 2011: First International Workshop on Trace Compilation August 24, 2011, Kongens Lyngby, Denmark Colocated with PPPJ 2011 === SCOPE === The first International Workshop on Trace Compilation (IWTC) aims to bring together researchers and practitioners who study trace compilation and

Re: [pypy-dev] os.tmpnam warnings

2011-06-06 Thread Amaury Forgeot d'Arc
Hi, 2011/6/6 Benjamin Peterson : > 2011/6/6 Da_Blitz : >>     """Return an absolute pathname of a file that did not exist at the >>     time the call is made.  The directory and a prefix may be specified >>     as strings; they may be omitted or None if not needed.""" >> +    from warnings import

Re: [pypy-dev] os.tmpnam warnings

2011-06-06 Thread Benjamin Peterson
2011/6/6 Da_Blitz : > Hi > > pypy 1.5 does not display a warning when using the os.tempnam and > os.tmpnam functions. use of these functions is not recommended as they > can cause security issues and hence python issues a RuntimeWarning > > > below is a patch to app_posix.py to make it act more lik

Re: [pypy-dev] os.tmpnam warnings

2011-06-06 Thread Maciej Fijalkowski
Can you post this to issue tracker? Patches on the mailing lists tend to get forgotten... On Mon, Jun 6, 2011 at 3:19 PM, Da_Blitz wrote: > Hi > > pypy 1.5 does not display a warning when using the os.tempnam and > os.tmpnam functions. use of these functions is not recommended as they > can cause

[pypy-dev] setpgrp and getpgrp platform:errors

2011-06-06 Thread Da_Blitz
Hi below is a patch that removes these errors during translation or when using py.py i am poking with things i do not fully understand here and would prefer it if someone told me i was an idiot and that args were passed to the functions for some reason (eg compatibility with the BSD's). accor

[pypy-dev] os.tmpnam warnings

2011-06-06 Thread Da_Blitz
Hi pypy 1.5 does not display a warning when using the os.tempnam and os.tmpnam functions. use of these functions is not recommended as they can cause security issues and hence python issues a RuntimeWarning below is a patch to app_posix.py to make it act more like cpython