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
When a constraint such as x + 1 = 10 is added to the path condition, then the value of x has effectively become concrete along that path. This can be detected (in this case that x = 9) and the concrete value can be written back to the state (memory or storage or stack). This ensures that subsequent accesses of that value return a cheap constant expression. Potentially generating less solver queries.
This feature would need a little research. When such situation is detected we need a way to search or reference back to where the expression came from or it is used in the state.
When a constraint such as x + 1 = 10 is added to the path condition, then the value of x has effectively become concrete along that path. This can be detected (in this case that x = 9) and the concrete value can be written back to the state (memory or storage or stack). This ensures that subsequent accesses of that value return a cheap constant expression. Potentially generating less solver queries.
This feature would need a little research. When such situation is detected we need a way to search or reference back to where the expression came from or it is used in the state.
The text was updated successfully, but these errors were encountered: