2422972eea
This would ensure that errno value is cleared out before test execution and tests pass even when LIBC_ERRNO_MODE_SYSTEM_INLINE is specified (and errno may be clobbered before test execution). A lot of the tests would fail, however, since errno would end up getting set to EDOM or ERANGE during test execution and never validated before the end of the test. This should be fixed - and errno should be explicitly checked or ignored in all of those cases, but for now add a TODO to address it later (see open issue #135320) and clear out errno in test fixture to avoid test failures.
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.