llvm-project

Author	SHA1	Message	Date
Chandler Carruth	278f89732f	Now that the analyzer is distinguishing between uninitialized uses that definitely have a path leading to them, and possibly have a path leading to them; reflect that distinction in the warning text emitted. llvm-svn: 129126	2011-04-08 06:33:38 +00:00
Ted Kremenek	ea6c20adaf	Take 2: merge -Wuninitialized-experimental into -Wuninitialized. Only must-be-uninitialized warnings are reported, with maybe-uninitialized under a separate flag. I await any fallout/comments/feedback, although hopefully this will produce no noise for users. llvm-svn: 127670	2011-03-15 05:22:33 +00:00
Ted Kremenek	e6a12a97d4	Move uninitialized variable checking back under -Wuninitialized-experimental. It is clear from user feedback that this warning is not quite ready. llvm-svn: 125007	2011-02-07 17:38:38 +00:00
Ted Kremenek	b3dbe28e31	Based on user feedback, swap -Wuninitialized diagnostics to have the warning refer to the bad use, and the note to the variable declaration. llvm-svn: 124758	2011-02-02 23:35:53 +00:00
Ted Kremenek	4058d87ad5	Teach -Wuninitialized about ObjC fast enumeration loops. llvm-svn: 124347	2011-01-27 02:01:31 +00:00