llvm-project.git/libc/test/UnitTest/LibcTest.cpp, branch users/nico/python-2

[libc] Add `-Wno-sign-conversion` & re-attempt `-Wconversion` (#129811)

2025-03-10T15:57:09+00:00

Relates to
https://github.com/llvm/llvm-project/issues/119281#issuecomment-2699470459

Revert "[libc] Enable -Wconversion for tests. (#127523)"

2025-03-05T21:42:40+00:00

This reverts commit 1e6e845d49a336e9da7ca6c576ec45c0b419b5f6 because it
changed the 1st parameter of adjust() to be unsigned, but libc itself
calls adjust() with a negative argument in align_backward() in
op_generic.h.

[libc] Enable -Wconversion for tests. (#127523)

2025-03-04T15:24:35+00:00

Relates to: #119281

[libc][stdfix] Implement fixed point bitsfx functions in llvm libc (#128413)

2025-02-27T18:05:27+00:00

Fixes #113359

---------

Signed-off-by: krishna2803

[libc][i386] FPBit support for 96b long double (#115084)

2024-11-12T16:19:47+00:00

`long double` is haunted on most architectures, but it is especially so on
i386-linux-gnu. While have 80b of significant data, on i386-linux-gnu this type
has 96b of storage.

Fixes for supporting printf family of conversions for `long double` on
i386-linux-gnu. This allows the libc-stdlib-tests and libc_stdio_unittests
ninja target tests to pass on i386-linux-gnu.

Fixes: #110894
Link: #93709
Co-authored-by: Michael Jones

[libc][NFC] Fix printed test time in 32-bit systems (#98922)

2024-07-15T16:16:02+00:00

clock() returns a clock_t, which is a long and might overflow in 32-bit
systems when the test takes a long time to run. Changing it to uint64_t
fixes this issue. Before:

[ RUN      ] LlvmLibcHashTest.Avalanche
[       OK ] LlvmLibcHashTest.Avalanche (18446744073709551138 ms)

After this patch:

[ RUN      ] LlvmLibcHashTest.Avalanche
[       OK ] LlvmLibcHashTest.Avalanche (4154 ms)

[libc] Migrate to using LIBC_NAMESPACE_DECL for namespace declaration (#98597)

2024-07-12T16:28:41+00:00

This is a part of #97655.

Revert "[libc] Migrate to using LIBC_NAMESPACE_DECL for namespace declaration" (#98593)

2024-07-12T07:12:13+00:00

Reverts llvm/llvm-project#98075

bots are broken

[libc] Migrate to using LIBC_NAMESPACE_DECL for namespace declaration (#98075)

2024-07-11T19:35:22+00:00

This is a part of #97655.

[libc] android atest compat (#93852)

2024-05-30T20:28:11+00:00

These changes slighly modify the output of the unittests so that they better
match GTest, so that utilities that parse the expected output from GTest (such
as Android's unit test harness) can read the output from our unit tests.

This allows our unit tests to be run on Android devices.

Add very primitive command line parsing to:
- support --gtest_color=no to disable printing terminal colors.
- recognize --gtest_print_time and print the test time in milliseconds.
  - most of our unit tests run on the order of microseconds, so its useful to
    preserve the existing behavior.  But upsteram GTest ONLY prints time tests
    in milliseconds, and Android's atest expects to be able to parse exactly
    that. Atest always passes --gtest_print_time. The word `took` is removed as
    that also differs from upstream GTest, tripping up parsers.
- ignore other --gtest_* flags

Do so so that atest can parse the output correctly.

Print the test number count before
each run, so that atest can parse this value correctly.

Link: https://android-review.googlesource.com/c/platform/external/llvm-libc/+/3107252
Link: https://google.github.io/googletest/advanced.html#colored-terminal-output
Link: https://google.github.io/googletest/advanced.html#suppressing-the-elapsed-time