bcm5719-llvm - Project Ortega BCM5719 LLVM

	Commit message (Collapse)	Author	Age	Files	Lines
*	Replace OwningPtr with std::unique_ptr.	Ahmed Charles	2014-03-07	1	-2/+3
\| \| \| \| \| \|	This compiles cleanly with lldb/lld/clang-tools-extra/llvm. llvm-svn: 203279
*	[C++11] Replace llvm::tie with std::tie.	Benjamin Kramer	2014-03-02	1	-1/+1
\| \| \| \|	llvm-svn: 202639
*	[analyzer] NonNullParamChecker: don't freak out about nested transparent_unions.	Jordan Rose	2014-02-26	1	-1/+3
\| \| \| \| \| \| \| \| \|	For now, just ignore them. Later, we could try looking through LazyCompoundVals, but we at least shouldn't crash. <rdar://problem/16153464> llvm-svn: 202212
*	Expose the name of the checker producing each diagnostic message.	Alexander Kornienko	2014-02-11	1	-3/+2
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Summary: In clang-tidy we'd like to know the name of the checker producing each diagnostic message. PathDiagnostic has BugType and Category fields, which are both arbitrary human-readable strings, but we need to know the exact name of the checker in the form that can be used in the CheckersControlList option to enable/disable the specific checker. This patch adds the CheckName field to the CheckerBase class, and sets it in the CheckerManager::registerChecker() method, which gets them from the CheckerRegistry. Checkers that implement multiple checks have to store the names of each check in the respective registerXXXChecker method. Reviewers: jordan_rose, krememek Reviewed By: jordan_rose CC: cfe-commits Differential Revision: http://llvm-reviews.chandlerc.com/D2557 llvm-svn: 201186
*	[analyzer] Teach NonNullParamChecker about 'nonnull' attributes on parameters.	Ted Kremenek	2014-01-17	1	-1/+7
\| \| \| \|	llvm-svn: 199473
*	[analyzer] Rename AttrNonNullChecker -> NonNullParamChecker	Anna Zaks	2013-03-09	1	-0/+193
	llvm-svn: 176755