bcm5719-llvm - Project Ortega BCM5719 LLVM

	Commit message (Collapse)	Author	Age	Files	Lines
*	Sort the remaining #include lines in include/... and lib/....	Chandler Carruth	2017-06-06	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	I did this a long time ago with a janky python script, but now clang-format has built-in support for this. I fed clang-format every line with a #include and let it re-sort things according to the precise LLVM rules for include ordering baked into clang-format these days. I've reverted a number of files where the results of sorting includes isn't healthy. Either places where we have legacy code relying on particular include ordering (where possible, I'll fix these separately) or where we have particular formatting around #include lines that I didn't want to disturb in this patch. This patch is entirely mechanical. If you get merge conflicts or anything, just ignore the changes in this patch and run clang-format over your #include lines in the files. Sorry for any noise here, but it is important to keep these things stable. I was seeing an increasing number of patches with irrelevant re-ordering of #include lines because clang-format was used. This patch at least isolates that churn, makes it easy to skip when resolving conflicts, and gets us to a clean baseline (again). llvm-svn: 304787
*	[libFuzzer] make __sanitizer_cov_trace_switch more predictable	Kostya Serebryany	2016-12-29	1	-2/+2
\| \| \| \|	llvm-svn: 290703
*	[libFuzzer] when tracing switch statements, handle only one case at a time ↵	Kostya Serebryany	2016-12-17	1	-2/+2
\| \| \| \| \| \|	(to make things faster). Also ensure that the signals from value profile do not intersect with the regular coverage llvm-svn: 290031
*	[libfuzzer] adding license headers to cpp files	Mike Aizatsky	2016-04-01	1	-0/+3
\| \| \| \| \| \|	Differential Revision: http://reviews.llvm.org/D18705 llvm-svn: 265174
*	[libFuzzer] make LLVMFuzzerTestOneInput (the fuzzer target function) return ↵	Kostya Serebryany	2015-10-02	1	-1/+2
\| \| \| \| \| \|	int instead of void. The actual return value is not yet used (and expected to be 0). This change is API breaking, so the fuzzers will need to be updated. llvm-svn: 249214
*	[libFuzzer] make sure that 2-byte arguments of switch() are handled properly	Kostya Serebryany	2015-07-31	1	-2/+21
\| \| \| \|	llvm-svn: 243781
*	[libFuzzer] support switch interception in dfsan mode	Kostya Serebryany	2015-07-31	1	-2/+2
\| \| \| \|	llvm-svn: 243760
*	[libFuzzer] trace switch statements and apply mutations based on the ↵	Kostya Serebryany	2015-07-31	1	-0/+35
	expected case values llvm-svn: 243726