On Sun, 18 Nov 2012 11:27:32 -0500
Benjamin Peterson wrote:
> 2012/11/18 Antoine Pitrou :
> > On Sun, 18 Nov 2012 09:37:57 -0500
> > Benjamin Peterson wrote:
> >
> >> 2012/11/18 Antoine Pitrou :
> >> > Also, I would point out that the reference counting behaviour is an
> >> > important feature of
2012/11/18 Antoine Pitrou :
> On Sun, 18 Nov 2012 09:37:57 -0500
> Benjamin Peterson wrote:
>
>> 2012/11/18 Antoine Pitrou :
>> > Also, I would point out that the reference counting behaviour is an
>> > important feature of *C*Python (to the point that we have test cases
>> > checking against refe
On Sun, 18 Nov 2012 09:37:57 -0500
Benjamin Peterson wrote:
> 2012/11/18 Antoine Pitrou :
> > Also, I would point out that the reference counting behaviour is an
> > important feature of *C*Python (to the point that we have test cases
> > checking against reference cycles), so we can't break it n
2012/11/18 Antoine Pitrou :
> Also, I would point out that the reference counting behaviour is an
> important feature of *C*Python (to the point that we have test cases
> checking against reference cycles), so we can't break it nilly-willy.
The tests about reference cycles are just tests that garb
On 17.11.12 03:13, Victor Stinner wrote:
The major drawback of the register approach (at least of my
implementation) is that it changes the lifetime of objects. Newly
created objects are only "destroyed" at the exit of the function,
whereas the stack-based VM destroys "immediatly" objects (thanks
On Sat, 17 Nov 2012 11:17:40 +0100
Armin Rigo wrote:
> Hi Victor,
>
> On Sat, Nov 17, 2012 at 2:13 AM, Victor Stinner
> wrote:
> > The major drawback of the register approach (at least of my implementation)
> > is that it changes the lifetime of objects. Newly created objects are only
> > "destr
-bounces+kristjan=ccpgames@python.org]
On Behalf Of Victor Stinner
Sent: 17. nóvember 2012 01:13
To: Python Dev
Subject: [Python-Dev] Register-based VM for CPython
The WPython project is similar to my work (except that it does not use
registers). It tries also to reduce the overhead of
Hi Victor,
On Sat, Nov 17, 2012 at 2:13 AM, Victor Stinner
wrote:
> The major drawback of the register approach (at least of my implementation)
> is that it changes the lifetime of objects. Newly created objects are only
> "destroyed" at the exit of the function, whereas the stack-based VM destro
Hi,
I'm still looking for the best approach to speedup CPython. I found the
following article comparing a stack-based VM to a register-based VM which
announces a speed up between 20% and 40% (depending if the instruction
dispatch uses a dummy switch or computed goto):
http://static.usenix.org/eve
