forked from OSchip/llvm-project
1170951c73
Some platforms don't support proper 128 bit integers, but some algorithms use them, such as any that use long doubles. This patch modifies the existing UInt class to support the necessary operators. This does not put this new class into use, that will be in followup patches. Reviewed By: sivachandra, lntue Differential Revision: https://reviews.llvm.org/D124959 |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| FPExceptMatcher.cpp | ||
| FPExceptMatcher.h | ||
| FPMatcher.cpp | ||
| FPMatcher.h | ||
| FuchsiaTest.h | ||
| LibcTest.cpp | ||
| LibcTest.h | ||
| LibcTestMain.cpp | ||
| MemoryMatcher.cpp | ||
| MemoryMatcher.h | ||
| PlatformDefs.h | ||
| PrintfMatcher.cpp | ||
| PrintfMatcher.h | ||
| README.md | ||
| StringUtils.h | ||
| Test.h | ||
README.md
The LLVM libc unit test framework
This directory contains a lightweight implementation of a gtest like unit test framework for LLVM libc.
Why not gtest?
While gtest is great, featureful and time tested, it uses the C and C++ standard libraries. Hence, using it to test LLVM libc (which is also an implementation of the C standard libraries) causes various kinds of mixup/conflict problems.
How is it different from gtest?
LLVM libc's unit test framework is much less featureful as compared to gtest. But, what is available strives to be exactly like gtest.
Will it be made as featureful as gtest in future?
It is not clear if LLVM libc needs/will need every feature of gtest. We only intend to extend it on an as needed basis. Hence, it might never be as featureful as gtest.