At 11:15 AM +0100 11/30/02, Jerome Quelin wrote:
You can rely on the registers not changing. We should probably have a push that doesn't guarantee preservation, but right now push[isnp] does. (And freshly documeted in pdd06 :)Hi,When I want to save all the integer registers, I'm using pushi, restoring them later with popi. When I'm doing a pushi, the old values of the registers are still present, but I'm wondering wether I can rely on this behavior, or if it's accidental and may be removed with another implementation?
The push[sinp] ops are all independent, working on separate stacks, so it doeesn't matter what order you do them in. (Though back to front on pops may be slightly more efficient, as you might have the newest pushed data still in cache). It's the save/restore ops that work on the common stack and need to watch ordering.Another question about pushi, pushs, etc. If I'm doing a pushi, then a pushs, does the order matter or not? ie, am I forced to do a pops then a popi, or can I do a popi and only after a pops? It seems to me that pushi and pushs are totally unrelated and I'm not forced to follow the order of the push, but I'd like to be sure...
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
