We do different kinds of screening for tail call stress and implicit tail calls, and this can lead to issues like dotnet/runtime#12833.
Because of this we are also missing the opportunity to tail call stress at tail call sites in inlinees. Seems like we ought to unify the logic if possible. It wasn't done earlier because information needed to qualify a tail call candidate is also needed for general call handling, and we didn't want to duplicate things.
BruceForstall
commented
5 years ago
We do different kinds of screening for tail call stress and implicit tail calls, and this can lead to issues like dotnet/runtime#12833.
Because of this we are also missing the opportunity to tail call stress at tail call sites in inlinees. Seems like we ought to unify the logic if possible. It wasn't done earlier because information needed to qualify a tail call candidate is also needed for general call handling, and we didn't want to duplicate things.
category:implementation theme:tail-call skill-level:intermediate cost:medium impact:small