Re: [Python-Dev] Register-based VM for CPython

2012-11-18 Thread Antoine Pitrou
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

Re: [Python-Dev] Register-based VM for CPython

2012-11-18 Thread Benjamin Peterson
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

Re: [Python-Dev] Register-based VM for CPython

2012-11-18 Thread 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 reference cycles), so we can't break it n

Re: [Python-Dev] Register-based VM for CPython

2012-11-18 Thread Benjamin Peterson
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

Re: [Python-Dev] Register-based VM for CPython

2012-11-18 Thread Serhiy Storchaka
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

Re: [Python-Dev] Register-based VM for CPython

2012-11-18 Thread Antoine Pitrou
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

Re: [Python-Dev] Register-based VM for CPython

2012-11-18 Thread Kristján Valur Jónsson
Interesting work indeed. From profiling CPython it has long been clear to me that enormous gains can be made by making instruction dispatching faster. A huge amount of time is spent in the evaluation loop. I have also been making small inroads to offline bytecode optimization. Identifying com

Re: [Python-Dev] Register-based VM for CPython

2012-11-17 Thread Armin Rigo
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