-
Notifications
You must be signed in to change notification settings - Fork 230
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #516 from AbsInt/value-analysis-pointer-comparison
More conservative value analysis of pointer equality
- Loading branch information
Showing
2 changed files
with
2 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Submodule test
updated
4 files
+5 −0 | export/.gitignore | |
+3 −1 | export/Makefile | |
+2 −0 | regression/Results/alias | |
+31 −1 | regression/alias.c |
62251c7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@xavierleroy FYI We also ran into a interesting case of over-precise pointer value analysis on embedded code that, admittedly, relied on undefined behavior.
https://gricad-gitlab.univ-grenoble-alpes.fr/sixcy/CompCert/-/commit/7544c6b9a71459799984059bdfb2029ccf992b44
62251c7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The link requires registration.
62251c7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh sorry @xavierleroy the externally accessible link is
https://gricad-gitlab.univ-grenoble-alpes.fr/certicompil/Chamois-CompCert/-/commit/7544c6b9a71459799984059bdfb2029ccf992b44
62251c7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the link. As discussed over email: before the merge of #516, it is indeed possible to have loops whose stopping condition is a pointer comparison to be "optimized" into infinite loops. I believe this cannot occur now that #516 is merged.