You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wrong - it turns out you can take the address of a variable spilled to the stack. It's done in (method 0 fact-info).
This seems like it won't be so bad to support in the decompiler. We can upgrade the stack-vars file to support this. Also should clear up "stack structure" vs. "stack variable".
In OpenGOAL we don't have any support for this yet. I think there are two parts to this:
Have a way to tell the compiler that a variable should be spilled onto the stack.
Allow taking the address of one of these.
The text was updated successfully, but these errors were encountered:
I was wrong - it turns out you can take the address of a variable spilled to the stack. It's done in
(method 0 fact-info)
.This seems like it won't be so bad to support in the decompiler. We can upgrade the stack-vars file to support this. Also should clear up "stack structure" vs. "stack variable".
In OpenGOAL we don't have any support for this yet. I think there are two parts to this:
The text was updated successfully, but these errors were encountered: