>
>Sfx, where possible, avoids this construct. There are, admittedly, some core
>opcodes that really do require the a-rate "if (bFirstTime)" guard. However,
>for non-oparray use of core opcodes, usually, pre-calculations of internal
>values derived from sub-arate arguments can be performed at the rate of the
>argument. This partly constitutes Sfx's motivation for moving sub-guard-rate
>opcode statements outside the the guard-block. It means that these internal
>state variables can be calculated without placing a conditional branch into
>the execution stream of the a-rate code.
Yes, even an interpreted approach like saint's one can have a small benefit
if the opcode is not decomposed into too many macro-instructions. This is
one reason why we did so, the other is that we broke all the opcodes into
nearly the half of meaningful functions.
Giorgio
__________________________________________________________________
Giorgio ZOIA
Integrated Systems Laboratory - DE/LSI - EPFL
CH-1015 Lausanne - SWITZERLAND
Phone: + 41 21 693 69 79 E-mail: Giorgio.Zoia@epfl.ch
Fax: +41 21 693 46 63
__________________________________________________________________
This archive was generated by hypermail 2b29 : Mon Jan 28 2002 - 12:03:55 EST