OSchip
/
llvm-project
mirror of https://github.com/THU-DSP-LAB/llvm-project.git
13
0
Fork 6
Code Issues Packages Projects Releases Wiki Activity
llvm-project/libc/utils/UnitTest
History
Tue Ly e138ad41e0 Update Test (EXPECT_EQ and friends) to accept __uint128_t and floating point types (float, double, long double). 
Summary: Update Test (EXPECT_EQ and friends) to accept __uint128_t and floating point types (float, double, long double).

Reviewers: sivachandra

Subscribers: mgorny, libc-commits

Tags: #libc-project

Differential Revision: https://reviews.llvm.org/D83931
 		2020-07-21 16:50:45 -04:00
..
CMakeLists.txt [libc] Add fully-qualified target names. 2020-04-10 18:01:52 -07:00
ErrnoSetterMatcher.h [libc][NFC] Make all top of file comments consistent. 2020-04-08 10:18:37 -07:00
README.md [libc] NFC: Fix trivial typo in comments, documents, and messages 2020-04-06 16:19:34 +09:00
Test.cpp Update Test (EXPECT_EQ and friends) to accept __uint128_t and floating point types (float, double, long double). 2020-07-21 16:50:45 -04:00
Test.h Update Test (EXPECT_EQ and friends) to accept __uint128_t and floating point types (float, double, long double). 2020-07-21 16:50:45 -04: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.