llvm-project.git/libc/test/src/string/strspn_test.cpp, branch main Unnamed repository; edit this file 'description' to name the repository. [libc] fixed signed char issues in strsep()/strtok()/strtok_r(). (#156705) 2025-09-03T18:00:38+00:00 enh-google enh@google.com 2025-09-03T18:00:38+00:00 ded5f433dedf4a3419548929ac3dfa826e11d2e1 Also add the missing tests for all the related functions (even the ones that were already right), and add the missing bazel build rules. 
Also add the missing tests for all the related functions (even the ones
that were already right), and add the missing bazel build rules.
 [libc] Don't rely on LIBC_HAS_SANITIZER when enabling null checks. (#150341) 2025-07-24T21:15:46+00:00 Alexey Samsonov vonosmas@gmail.com 2025-07-24T21:15:46+00:00 5e01797cd035cd1b86beb0ad3fb24277531dff66 LIBC_HAS_SANITIZER (which is defined if ASan, MSan, or UBSan is enabled) is currently used to implicitly disable null checks, normally enabled via LIBC_ADD_NULL_CHECKS config value. Remove this condition, and rely purely on the config value instead: * LIBC_HAS_SANITIZER will be true even for UBSan modes which doesn't rely on null checks at all (e.g. -fsanitize=alignment) * null checks today (implemented via __builtin_trap) should function normally today even when sanitizer is enabled - trap is still a trap * tests have been migrated to WITH_SIGNAL(-1) which doesn't prescript a particular signal / exit-code, and thus should pass even if sanitizers override the default ones. 
LIBC_HAS_SANITIZER (which is defined if ASan, MSan, or UBSan is enabled)
is currently used to implicitly disable null checks, normally enabled
via LIBC_ADD_NULL_CHECKS config value. Remove this condition, and rely
purely on the config value instead:

* LIBC_HAS_SANITIZER will be true even for UBSan modes which doesn't
rely on null checks at all (e.g. -fsanitize=alignment)
* null checks today (implemented via __builtin_trap) should function
normally today even when sanitizer is enabled - trap is still a trap
* tests have been migrated to WITH_SIGNAL(-1) which doesn't prescript a
particular signal / exit-code, and thus should pass even if sanitizers
override the default ones.
 [libc] Expand usage of libc null checks. (#116262) 2025-06-04T17:08:27+00:00 Aly ElAshram 71949028+AlyElashram@users.noreply.github.com 2025-06-04T17:08:27+00:00 ff844df719d7226a46b8cb0d99aef9480cced247 Fixes #111546 --------- Co-authored-by: alyyelashram <150528548+alyyelashram@users.noreply.github.com> 
Fixes #111546

---------

Co-authored-by: alyyelashram <150528548+alyyelashram@users.noreply.github.com>
 [libc] Mass replace enclosing namespace (#67032) 2023-09-26T09:45:04+00:00 Guillaume Chatelet gchatelet@google.com 2023-09-26T09:45:04+00:00 b6bc9d72f65a5086f310f321e969d96e9a559e75 This is step 4 of https://discourse.llvm.org/t/rfc-customizable-namespace-to-allow-testing-the-libc-when-the-system-libc-is-also-llvms-libc/73079 
This is step 4 of
https://discourse.llvm.org/t/rfc-customizable-namespace-to-allow-testing-the-libc-when-the-system-libc-is-also-llvms-libc/73079
 [libc][NFC] Move UnitTest and IntegrationTest to the 'test' directory. 2023-02-07T19:45:51+00:00 Siva Chandra Reddy sivachandra@google.com 2023-02-06T07:07:23+00:00 af1315c28f9bab76d3c2e1492a3d41e7c48215f8 This part of the effort to make all test related pieces into the `test` directory. This helps is excluding test related pieces in a straight forward manner if LLVM_INCLUDE_TESTS is OFF. Future patches will also move the MPFR wrapper and testutils into the 'test' directory. 
This part of the effort to make all test related pieces into the `test`
directory. This helps is excluding test related pieces in a straight
forward manner if LLVM_INCLUDE_TESTS is OFF. Future patches will also move
the MPFR wrapper and testutils into the 'test' directory.
[libc][NFC] add "LlvmLibc" as a prefix to all test names 2021-01-20T23:15:36+00:00 Michael Jones michaelrj@google.com 2021-01-15T21:54:23+00:00 1df0dbfcb5c0b90299fe5b74caf42e4cacce16fc Summary: Having a consistent prefix makes selecting all of the llvm libc tests easier on any platform that is also using the gtest framework. This also modifies the TEST and TEST_F macros to enforce this change moving forward. Reviewers: sivachandra Subscribers: 
Summary:
Having a consistent prefix makes selecting all of the llvm libc tests
easier on any platform that is also using the gtest framework.
This also modifies the TEST and TEST_F macros to enforce this change
moving forward.

Reviewers: sivachandra

Subscribers:
[libc] Add strspn implementation and std::bitset 2020-08-05T20:48:38+00:00 cgyurgyik gyurgyikcp@gmail.com 2020-08-05T20:36:52+00:00 f3b41502554f2948ad00531dde7c3f53973de960 Reviewed By: sivachandra, abrachet Differential Revision: https://reviews.llvm.org/D85103 
Reviewed By: sivachandra, abrachet

Differential Revision: https://reviews.llvm.org/D85103