Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update interface of getCallToReturnFlowFunction #5

Closed
ericbodden opened this issue Jun 19, 2018 · 1 comment
Closed

Update interface of getCallToReturnFlowFunction #5

ericbodden opened this issue Jun 19, 2018 · 1 comment
Labels
enhancement New feature or request

Comments

@ericbodden
Copy link
Member

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?

@ericbodden ericbodden added the enhancement New feature or request label Jun 19, 2018
@pdschubert
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants