Files

Mikhail R. Gadelha 8fc87f54a8 [libc][NFC] Couple of small warning fixes (#67847 )

This patch fixes a couple of warnings when compiling with gcc 13:

* CPP/type_traits_test.cpp: 'apply' overrides a member function but is
not marked 'override'
* UnitTest/LibcTest.cpp:98: control reaches end of non-void function
* MPFRWrapper/MPFRUtils.cpp:75: control reaches end of non-void function
* smoke/FrexpTest.h:92: backslash-newline at end of file
* __support/float_to_string.h:118: comparison of unsigned expression in ‘>= 0’ is always true
* test/src/__support/CPP/bitset_test.cpp:197: comparison of unsigned expression in ‘>= 0’ is always true

---------

Signed-off-by: Mikhail R. Gadelha <mikhail@igalia.com>

2023-10-02 19:29:26 -04:00

BazelFilePath.cpp

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

CmakeFilePath.cpp

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

CMakeLists.txt

[libc][Obvious] Remove the previous ErrnoSetterMatcher target. (#67469 )

2023-09-26 11:01:21 -07:00

ErrnoSetterMatcher.h

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

ExecuteFunction.h

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

ExecuteFunctionUnix.cpp

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

FPExceptMatcher.cpp

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

FPExceptMatcher.h

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

FPMatcher.h

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

FuchsiaTest.h

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

HermeticTestUtils.cpp

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

LibcDeathTestExecutors.cpp

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

LibcTest.cpp

[libc][NFC] Couple of small warning fixes (#67847 )

2023-10-02 19:29:26 -04:00

LibcTest.h

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

LibcTestMain.cpp

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

MemoryMatcher.cpp

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

MemoryMatcher.h

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

PigweedTest.h

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

PlatformDefs.h

…

PrintfMatcher.cpp

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

PrintfMatcher.h

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

README.md

…

RoundingModeUtils.cpp

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

RoundingModeUtils.h

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

ScanfMatcher.cpp

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

ScanfMatcher.h

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

StringUtils.h

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

Test.h

[libc][NFC] Fixing various typos

2023-05-31 12:11:09 +00:00

TestLogger.cpp

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

TestLogger.h

[libc] Mass replace enclosing namespace (#67032 )

2023-09-26 11:45:04 +02:00

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.