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

Make HeapSeparator work #197

Closed
alexandernutz opened this issue Jun 28, 2017 · 1 comment
Closed

Make HeapSeparator work #197

alexandernutz opened this issue Jun 28, 2017 · 1 comment

Comments

@alexandernutz
Copy link
Member

After the latest rework of the VPDomain/equality domain (see #178), we might finally get enough sensible input for the HeapSeparator to run it on some practical input.
"in principle" the HeapSeparator should work, but there will still be many details to improve/correct.

@alexandernutz alexandernutz self-assigned this Jun 28, 2017
alexandernutz added a commit that referenced this issue Jul 1, 2017
 - now deals with Terms instead of IProgramVarOrConsts and EqNodes, by and large
 - finds out accessing indices on its own now (in HeapSepPreAnalysisVisitor), still asks VPDomainPreanalysis which arrays are tracked
 - an array index is a List of terms now (multidimensional case)
alexandernutz added a commit that referenced this issue Jul 15, 2017
alexandernutz added a commit that referenced this issue Oct 15, 2017
alexandernutz added a commit that referenced this issue Oct 16, 2017
alexandernutz added a commit that referenced this issue Jan 9, 2018
@alexandernutz
Copy link
Member Author

closing in favour of the more specific #295

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