How the Cinder JIT's function inliner helps us optimize Instagram

maybe someone will see this (since the OP is about inlining) and give me good ideas: i would like to do loop carried dependency analysis through functions calls e.g., `foo` has a loop nest that calls `bar` that has a loop nest that modifies state in `foo` that affects foo's loop nest. my naive, off-top-of-my-head, idea was to inline `bar` and perform the analysis.

now i'm sure this goes wrong for real code in a billion different ways, but is there something i'm not considering regarding the principle (i.e. something at the intersection of inlining and dependency analysis)?