Documentation

Emit code for a foreign call, and return the results to the sequel. Precondition: the length of the arguments list is the same as the arity of the foreign function.

Produce code to save the current thread state to CurrentTSO

Save STG registers

STG registers must be saved around a C call, just in case the STG register is mapped to a caller-saves machine register. Normally we don't need to worry about this the code generator has already loaded any live STG registers into variables for us, but in hand-written low-level Cmm code where we don't know which registers are live, we might have to save them all.

Restore STG registers (see emitSaveRegs)

Push a subset of STG registers onto the stack, specified by the bitmap

Sometimes, a "live" subset of the STG registers needs to be saved on the stack, for example when storing an unboxed tuple to be used in the GHCi bytecode interpreter.

The "live registers" bitmap corresponds to the list of registers given by tupleRegsCover, with the least significant bit indicating liveness of the first register in the list.

Each register is saved to a stack slot of one or more machine words, even if the register size itself is smaller.

The resulting Cmm code looks like this, with a line for each real or virtual register used for returning tuples:

... if((mask & 2) != 0) { Sp_adj(-1); Sp(0) = R2; } if((mask & 1) != 0) { Sp_adj(-1); Sp(0) = R1; }

See Note [GHCi tuple layout]

Pop a subset of STG registers from the stack (see emitPushTupleRegs)

Produce code to load the current thread state from CurrentTSO