| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
These consistency violations originate from the VariableCapture instantation in C#, JS, Python, and Ruby.
The previously-added consistency errors are gone.
Unified also had consistency errors from its LocalSSA instantiation, due to its use of synthetic read nodes to represent post-update positions. Many variables can have a post-update at the same CFG node.
Many tests passed for the wrong reasons, due to the SSA bug. We need more library/operator modelling to actually find these flows.
Switched to TaintTracking and adds some very ad-hoc steps to recover most of the results. Some more tests pass and others fail; these are now consistent with what we actually model.
The C++ instantiation of DataFlowIntegration generated a bad join order
Since the callee itself is now always considered to be an argument, it needs to have a post-update node. This only matters when the callee is a function with captures, but it should be harmless in general.
| /** | ||
| * The given `read` reads multiple variables at once. `var` is bound to one of them. | ||
| */ |
| Back | FazBrowse Home | New Git URL |
No description provided.