> How about instead of treating the arguments as an array we treat them as > a stack? There could be functions getFirstSyscallArg and > getNextSyscallArg. The first resets the stack pointer to the first > argument, and both increment it appropriately depending on what they > just returned. A form with no argument will use the "default" size, most > likely one register, and a form with an argument can decide what special > behavior is necessary based on that argument. For instance, it sounds > like that argument could be the width of the operand. If it's 64, then > sometimes the pointer will be incremented differently, register values > combined, etc.
I don't know the code super well, but I'd think it possible to process arguments in order without too much trouble. Given the C calling convention, it would be extraordinarily odd to have a later argument define the semantics of an earlier one. Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
