So the parm_start section is:
-1st parameters (if they exist)
-2nd locals (if they exist)
-3rd statement scratchpad (if needed)
I'm guessing by 'temps' you are referring to what I call a 'scratchpad'. Basically where it writes results of one statement to be used by the next statement.
I haven't gotten into how it deals with the stack just yet.
I've written a program to automate the dis-assembly so now I have all functions with their corresponding function names, source file names, and statements (each with op code names.) My questions currently are:
-is edict self always 0x1c? If not how do you correspond 0x1c with self?
-is field .impulse always 0xad? (I assume this is a byte offset from the beginning of the structure.)
-the parameters/locals/scratchpad numbers I assume to be offsets from a block, but where is this block?
-do function calls refer to function index, function byte_offset, statement index, or statement byte_offset?
P.S. might want to clear your PMs: Spike has exceeded their stored private messages quota and cannot accept further messages until they clear some space.
-1st parameters (if they exist)
-2nd locals (if they exist)
-3rd statement scratchpad (if needed)
I'm guessing by 'temps' you are referring to what I call a 'scratchpad'. Basically where it writes results of one statement to be used by the next statement.
I haven't gotten into how it deals with the stack just yet.
I've written a program to automate the dis-assembly so now I have all functions with their corresponding function names, source file names, and statements (each with op code names.) My questions currently are:
-is edict self always 0x1c? If not how do you correspond 0x1c with self?
-is field .impulse always 0xad? (I assume this is a byte offset from the beginning of the structure.)
-the parameters/locals/scratchpad numbers I assume to be offsets from a block, but where is this block?
-do function calls refer to function index, function byte_offset, statement index, or statement byte_offset?
P.S. might want to clear your PMs: Spike has exceeded their stored private messages quota and cannot accept further messages until they clear some space.
Comment