-
Notifications
You must be signed in to change notification settings - Fork 2
Memory transform #377
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
Memory transform #377
Conversation
c5e15b9
to
3b149d7
Compare
3a65580
to
cc83b68
Compare
5c69dc7
to
2440870
Compare
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 variable names in the output aren't going to be valid boogie identifiers, they should probably be renamed in the transform
@@ -0,0 +1,530 @@ | |||
Project(Attrs([Attr("filename","\"clasloc.out\""), |
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.
If we are only checking in results from one lifter can we use the gtirb results rather than BAP
15e8e0a
to
be31a91
Compare
do i need to update ResolveSpec in IRtoBoogie to have the spec include accesses to globals which have been transformed to a scalar |
Yeah I think so |
…ted with their index expression
… to be in/out parameters
87f3e39
to
8c57a40
Compare
095bb4d
to
7a851c7
Compare
Don't need to fix for this PR but afterward I have TODO
|
StackIdentification should be disabled by --memory-transform probably, its further splitting the memory but probably not soundly BASIL/src/main/scala/util/RunUtils.scala Lines 321 to 324 in 7a851c7
e.g. with It seems like DSA already splits it into stack and heap when it can't do the local stack variable transform with |
…nstead of being replaced by scalars
Transforms memory accesses to register assignments using the results of DSA when --memory-transform flag is set
(requires --simplify and --dsa norm)