bcm5719-llvm - Project Ortega BCM5719 LLVM

	Commit message (Collapse)	Author	Age	Files	Lines
...
*	Initial version of clang-tidy check to use override instead of virual.	Daniel Jasper	2014-05-16	1	-0/+4
\| \| \| \| \|	Review: http://reviews.llvm.org/D3688 llvm-svn: 208954
*	Add clang-tidy check to remove redundant .get() calls on smart pointers.	Samuel Benzaquen	2014-03-27	1	-3/+7
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Summary: This check finds and removes redundant .get() calls on smart pointers. Example: ptr.get()->Foo() ==> ptr->Foo() Reviewers: alexfh CC: cfe-commits Differential Revision: http://llvm-reviews.chandlerc.com/D3186 llvm-svn: 204947
*	Add an argument comment checker to clang-tidy.	Peter Collingbourne	2014-03-18	1	-0/+4
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This checks that parameters named in comments that appear before arguments in function and constructor calls match the parameter name used in the callee's declaration. For example: void f(int x, int y); void g() { f(/y=/0, /z=/0); } contains two violations of the policy, as the names 'x' and 'y' used in the declaration do not match names 'y' and 'z' used at the call site. I think there is significant value in being able to check/enforce this policy as a way of guarding against accidental API misuse and silent breakages caused by API changes. Although this pattern appears somewhat frequently in the LLVM codebase, this policy is not prescribed by the LLVM coding standards at the moment, so it lives under 'misc'. Differential Revision: http://llvm-reviews.chandlerc.com/D2914 llvm-svn: 204113
*	Added a module for checks not related to LLVM or Google coding style.	Alexander Kornienko	2014-03-05	1	-0/+32
	llvm-svn: 202970