infer_clone

History

Jules Villard 6a738045fd [pulse] interprocedural histories and traces Summary: bigmacro_bender There are 3 ways pulse tracks history. This is at least one too many. So far, we have: 1. "histories": a humble list of "events" like "assigned here", "returned from call", ... 2. "interproc actions": a structured nesting of calls with a final "action", eg "f calls g calls h which does blah" 3. "traces", which combine one history with one interproc action This diff gets rid of interproc actions and makes histories include "nested" callee histories too. This allows pulse to track and display how a value got assigned across function calls. Traces are now more powerful and interleave histories and interproc actions. This allows pulse to track how a value is fed into an action, for instance performed in callee, which itself creates some more (potentially now interprocedural) history before going to the next step of the action (either another call or the action itself). This gives much better traces, and some examples are added to showcase this. There are a lot of changes when applying summaries to keep track of histories more accurately than was done before, but also a few simplifications that give additional evidence that this is the right concept. Reviewed By: skcho Differential Revision: D17908942 fbshipit-source-id: 3b62eaf78		5 years ago
..
annotations	[lockless] detect lock acquisitions from methods annotated @Lockless	5 years ago
etc	[clang] replace yojson frontend with biniou frontend	9 years ago
lib	[cost][inferbo] Add models for androidx.collection	5 years ago
man/man1	[config] saner names and doc for blacklist options	5 years ago
models	[biabd] rename models-related things to "biabduction-..."	5 years ago
src	[pulse] interprocedural histories and traces	5 years ago
tests	[pulse] interprocedural histories and traces	5 years ago
.ocp-indent	add ocp-indent configuration and eclipse launcher	9 years ago