At 10:57 PM 3/29/2001 +0100, Piers Cawley wrote: >How painful would an 'potential' optimization that marked that area in >the bytecode/optree/whatever, with something along the lines of the >following be? > > If you get to this point and $i is not tied, and '=' is not > overridden for $i's class > then $i = 1000 > otherwise, do the loop. I've considered an "iftied" opcode that would essentially do this. The downside is the extra size of the bytecode as you've mentioned. I'm not sure if the speed boost would be worth it, but it's on my list of things to try. Dan --------------------------------------"it's like this"------------------- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
- Re: What can we optimize (was Re: Schwartzian transform... Dan Sugalski
- Re: What can we optimize (was Re: Schwartzian transform... Dan Sugalski
- Re: What can we optimize (was Re: Schwartzian tran... Jarkko Hietaniemi
- Re: What can we optimize (was Re: Schwartzian transform... Dan Sugalski
- Re: What can we optimize (was Re: Schwartzian transform... Hong Zhang
- Re: What can we optimize (was Re: Schwartzian tran... Juanma Barranquero
- Re: What can we optimize (was Re: Schwartzian transform... James Mastros
- Re: What can we optimize (was Re: Schwartzian transform... Piers Cawley
- Re: What can we optimize (was Re: Schwartzian transform... Russ Allbery
- Re: What can we optimize (was Re: Schwartzian transform... Dan Sugalski
- Re: What can we optimize (was Re: Schwartzian tran... David L. Nicol
- Re: What can we optimize (was Re: Schwartzian transform... Uri Guttman
- RE: What can we optimize (was Re: Schwartzian transform... David Whipp