Rafael Espindola 506c684d55 Don't check for null after calling COFFObjectFile::toSec. ... It can only return null if passed a corrupted reference with a null Ref.p. Checking for null is then an issue for asserts to check for internal consistency, not control flow to check for invalid input. I didn't add an assert(sec != nullptr) because toSec itself has a far more complete assert. llvm-svn: 219235		2014-10-07 21:03:22 +00:00
clang	Objective-C SDK modernization. When modernizing to	2014-10-07 19:01:46 +00:00
clang-tools-extra	Make clang-tidy's runCheckOnCode actually use the DiagnosticConsumer.	2014-10-07 15:49:36 +00:00
compiler-rt	Avoid bashisms and switch to /bin/sh	2014-10-07 20:23:57 +00:00
debuginfo-tests	relax testcase for LLDB output format compatibility.	2014-03-19 23:06:18 +00:00
libclc	Implement log1p builtin	2014-10-07 20:22:42 +00:00
libcxx	Fix win32 support header for mingw32.	2014-10-06 20:06:33 +00:00
libcxxabi	Use __atomic_exchange_n instead of Clang's __sync_swap	2014-10-03 20:03:47 +00:00
lld	[PECOFF] Infer machine type from input object file	2014-10-07 01:38:46 +00:00
lldb	This test case was incorrect, it was relying on the fact	2014-10-07 20:59:00 +00:00
llvm	Don't check for null after calling COFFObjectFile::toSec.	2014-10-07 21:03:22 +00:00
openmp	I apologise in advance for the size of this check-in. At Intel we do	2014-10-07 16:25:50 +00:00
polly	[Fix] Non i1 typed select condition for weird pw aff functions.	2014-10-07 14:37:59 +00:00