C++: instruction -> operand field flow#4573
Conversation
… now go from instructions and operands. There are a couple of read steps that still target instructions because I couldn't decide on an operand to target.
|
The failing tests all look like changes in path explanation in the internal repo. Once the changes here have been approved I'll make an internal PR. |
dbartol
left a comment
There was a problem hiding this comment.
A few questions and a few comments.
Would you mind waiting to merge this until the temporary object PR is merged? I don't think we have any merge conflicts quite yet, but we'll probably conflict on those path explanation tests in the private repo, and your PR may provoke real analysis change in mine.
That's a good point. I'll let this PR wait until your temporary object PR is merged. |
Performance looks alright. The only worry is a 4% analysis-time increase on |
3c77886 to
177f943
Compare
This PR changes
readStepso that it performsinstruction -> operandflow, andstoreStepso that it performsoperand -> instructionflow. This matches better with the way we do simple flow steps.CPP-differences: https://jenkins.internal.semmle.com/job/Changes/job/CPP-Differences/1527/