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.

Jia Chen a6757be036 Force emitting prune node for C++ comparison expressions ... Summary: This diff tries to achieve the followings: if we have the following C++ codes: ``` bool foo(int x, int y) { return &x == &y; } ``` We want the C++ frontend to emit Sil as if the input is written as ``` bool foo(int x, int y) { if (&x == &y) return 1; else return 0; } ``` This matches the behavior of our Java frontend. The reason why we prefer an explicit branch is that it will force the backend to eagerly produce two different specs for `foo`. Without the explicit branch, for the above example the backend would produce one spec with `return = (&x == &y)` as the post condition, which is not ideal because (1) we don't want local variables to escape to the function summary, and (2) with the knowledge that no two local variables may alias each other, the backend could actually determines that `&x == &y` is always false, emitting a more precise postcondition `return = 0`. This is not possible if we do not eagerly resolve the comparison expression. Reviewed By: akotulski Differential Revision: D5260745 fbshipit-source-id: 6bbbf99		8 years ago
..
bufferoverrun	[Bufferoverrun] symbolic value for parameter	8 years ago
errors	Teach the frontend to recognize STL throw wrappers	8 years ago
frontend	Force emitting prune node for C++ comparison expressions	8 years ago
quandary	[quandary] only report code injection via endpoints on strings	8 years ago
shared	Force emitting prune node for C++ comparison expressions	8 years ago
siof	[infer][checkers] remove the siof analyzer option and rely on the --siof flag only	8 years ago
threadsafety	[ThreadSafety] Do not report if all accesses are unprotected.	8 years ago