David Blaikie 453f4f0130 Use only explicit bool conversion operators ... BitVector/SmallBitVector::reference::operator bool remain implicit since they model more exactly a bool, rather than something else that can be boolean tested. The most common (non-buggy) case are where such objects are used as return expressions in bool-returning functions or as boolean function arguments. In those cases I've used (& added if necessary) a named function to provide the equivalent (or sometimes negative, depending on convenient wording) test. One behavior change (YAMLParser) was made, though no test case is included as I'm not sure how to reach that code path. Essentially any comparison of llvm::yaml::document_iterators would be invalid if neither iterator was at the end. This helped uncover a couple of bugs in Clang - test cases provided for those in a separate commit along with similar changes to `operator bool` instances in Clang. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181868 91177308-0d34-0410-b5e6-96231b3b80d8		2013-05-15 07:36:59 +00:00
..
ADT	Fix a bug that APFloat::fusedMultiplyAdd() mistakenly evaluate "14.5f * -14.5f + 225.0f" to 225.0f.	2013-05-13 18:03:12 +00:00
Analysis
Bitcode
DebugInfo	Create a stub for DWARF parser unittests	2013-04-17 08:29:02 +00:00
ExecutionEngine	Use only explicit bool conversion operators	2013-05-15 07:36:59 +00:00
IR	Add missing PatternMatch.cpp to CMakeLists.txt	2013-05-05 02:14:28 +00:00
Option
Support	Get the unittests compiling when building with cmake and the setting	2013-05-14 13:29:16 +00:00
Transforms
CMakeLists.txt	Create a stub for DWARF parser unittests	2013-04-17 08:29:02 +00:00
Makefile	Create a stub for DWARF parser unittests	2013-04-17 08:29:02 +00:00
Makefile.unittest