Skip to content

Helpers

Building blocks for optimizations that change the calling convention

Some optimizations break the calling convention (how a function receives its arguments).
For example:

These need the same answers again and again:

  • Where does ESP point at each instruction?
  • Which argument slots can we recognize?
  • Which arguments get written to the stack before a call?
  • Can we find and rewrite every caller?

The helpers I made answer those, so each optimization doesn't have to.

Where this happens

codegen/optimizations/helpers/, under src/xbox-recomp2/src/.

The helpers

Helper Answers
Stack Tracking Where do ESP and EBP point before each instruction?
Function Stacks How does each call move ESP?
Stack Arguments Which slots are recognized, and who removes them?
Entry Loads Which arguments get read off the stack at the start?
Call Setup Which arguments get writte n to the stack before a call?
Known Callers Can we find and rewrite every caller?
Stack Shift Move every stack access above some point by N bytes.
Flag Effects Which EFLAGS does one instruction read and write?
Flag Boundaries Which EFLAGS cross each call and ret?
Needed Flags Which EFLAGS must be valid after each operation?
Loops Which loops does a function have?

Remarks

Should be obvious, but these helpers aren't updated in real time, if you change the code from a pass; you gotta recompute.