You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

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
..
GlobalTest.java	[impurity] Add initial Java support and don't run pulse twice	5 years ago
Localities.java	[impurity] Add initial Java support and don't run pulse twice	5 years ago
Makefile	[impurity] Add initial Java support and don't run pulse twice	5 years ago
PurityModeled.java	[impurity] Add initial Java support and don't run pulse twice	5 years ago
Test.java	[impurity] Add initial Java support and don't run pulse twice	5 years ago
issues.exp	[pulse] interprocedural histories and traces	5 years ago