History

michaelrj-google 3eb1e6d8e9

[libc] Move libc_errno inside of LIBC_NAMESPACE (#80774 )

Having libc_errno outside of the namespace causes versioning issues when
trying to link the tests against LLVM-libc. Most of this patch is just
moving libc_errno inside the namespace in tests. This isn't necessary in
the function implementations since those are already inside the
namespace.

2024-02-06 10:36:05 +01: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] Allow hermetic timing if the clock function is built (#71092 )

2023-11-02 15:03:17 -05:00

ErrnoSetterMatcher.h

[libc] Move libc_errno inside of LIBC_NAMESPACE (#80774 )

2024-02-06 10:36:05 +01: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] Move libc_errno inside of LIBC_NAMESPACE (#80774 )

2024-02-06 10:36:05 +01:00

FuchsiaTest.h

[libc] Move libc_errno inside of LIBC_NAMESPACE (#80774 )

2024-02-06 10:36:05 +01:00

HermeticTestUtils.cpp

[libc] Replace -nostdlib++ flag when building with gcc and add placement new operator to HermeticTestUtils.cpp. (#78906 )

2024-01-22 19:27:27 -05:00

LibcDeathTestExecutors.cpp

[libc] Mass replace enclosing namespace (#67032 )

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

LibcTest.cpp

[libc] Allow hermetic timing if the clock function is built (#71092 )

2023-11-02 15:03:17 -05:00

LibcTest.h

[libc] Move libc_errno inside of LIBC_NAMESPACE (#80774 )

2024-02-06 10:36:05 +01: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][NFC] Rename MANTISSA_WIDTH in FRACTION_LEN (#75489 )

2023-12-15 13:57:35 +01: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.