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

Switch upper/lower bounds #28

Open
florian-kuebler opened this issue Jan 24, 2020 · 0 comments
Open

Switch upper/lower bounds #28

florian-kuebler opened this issue Jan 24, 2020 · 0 comments
Assignees

Comments

@florian-kuebler
Copy link
Collaborator

Within FPCF, bottom is the "worst" value, or most imprecise value, and top is the best/most precise one.
E.g. for a call graph, bottom is the set of all edges, and top the empty set.
Thus, a lower bound would be the set of edges that can be included at worst, an the upper-bound the set that must be included according to the analysis.
In most related work, in particular in the field of abstract interpretation, this is vise-versa.

We should refactor the whole framework as well as all analyses, such that we use the terms common in literature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants