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 525a94e470 [siof] do not generate dummy derefs in initializer code ... Summary: This confuses the SIOF checker and causes false positives. This dummy deref is generated for constructors of classes that are modeled as being pointer types instead of the actual class in infer, typically for smart pointers. I do not understand how this works. The biabduction also analyses this code, so might now get confused itself. Reviewed By: jberdine Differential Revision: D6221817 fbshipit-source-id: 050c5a9		7 years ago
..
bufferoverrun	[inferbo] revise semantics of vector::data	7 years ago
errors	[infer][biabduction] remove the bi-abduction based check for uninitialized values	7 years ago
frontend	[siof] one access per sink, better report deduplication	7 years ago
liveness	[dead stores] don't warn on likely-harmless dead stores to default values	7 years ago
nullable	[infer][nullable checker] only report once when the return of a nullable method is derferenced several times	7 years ago
quandary	[quandary] handle taint propagation in copying of structs/via derefs of pointers to structs	7 years ago
racerd	[LockConsistency] Adding ownership of locals for c-style functions	7 years ago
shared	[clang] static data members are external globals unless defined in the file	7 years ago
siof	[siof] do not generate dummy derefs in initializer code	7 years ago
uninit	[uninit] Reporting parameters calls which are not passed by reference	7 years ago