You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
getCallFlowFunction is currently called once separately for every call target. This is how it should be.
getCallToReturnFlowFunction, however, is called only once per call site, getting a set of call targets instead. I think that's quite inconsistent. Is there a good reason for not doing it as in getCallFlowFunction?
The text was updated successfully, but these errors were encountered:
The reason is that getCallFlowFunction handles inter-procedural flows to the possible callees whereas getCallToRetFlowFunction handles intra-procedural flows alongside a given call-site - while there is (usually) only one possible path to be taken.
getCallFlowFunction is currently called once separately for every call target. This is how it should be.
getCallToReturnFlowFunction, however, is called only once per call site, getting a set of call targets instead. I think that's quite inconsistent. Is there a good reason for not doing it as in getCallFlowFunction?
The text was updated successfully, but these errors were encountered: