If there's a region of the stack reserved for potential tail call arguments (only the case when we guarantee tail calls will be honoured), this is right next to the incoming stored return address, not necessarily next to the callee-saved area, so combining the two into a single figure leads to incorrect offsets in some edge cases.
This keeps the two concepts split and (hopefully) updates all users of getCalleeSavedFrameSize that need it. The notable exceptions are the stack-realignment code in emitEpilogue (~line 2117) which is where the bug came from, and Windows-ABI functions, because they don't guarantee tail calls so it should always be zero there.
Similarly, the code in getFrameIndexReference that dealt with this delta wasn't present on the realigned stack branch so I refactored it so that wasn't possible any more.
clang-format: please reformat the code