Dan Sugalski <[EMAIL PROTECTED]> wrote: > Okay, here's a really, really evil idea. (And yes, bluntly, it's > triggered by the pie-thon bytecode translator's needs) I need a > stack,
Do you? I've converted all stack stuff at compile time, till now. I don't see the point, why this might not work for all opcodes. > ... and one that's faster than our current stack which, while > snappy for what it does, is still burdened by generality. I also need > a stack that's generally not very big. So... Generally. Have a look at BUILD_TUPLE or BUILD_LIST. The limited stack will not work, you have to do overflow checking all the time and you'll have 2 addressing modes, one in registers and one in overflow. > iset Px, Iy > This does a set of register Px to PMC register #Y. C<setp_ind> *is* in set.ops. If above is the other direction, then that should be named accordingly. leo
