At this point in determineCalleeSaves, try to get a first estimate of the number of register that will be backed up, to estimate whether a stack probe is going to be needed later or not.
I ran into a case with a function that wouldn't otherwise back up R4 at all, clobbering it with the stack probe call. And apparently one existing test case forgot to back up LR even though it calls the chkstk function within the test.