llvm-project.git/libc/test/src/string/strcat_test.cpp, branch main Unnamed repository; edit this file 'description' to name the repository. [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][NFC] Make all top of file comments consistent. 2020-04-08T17:18:37+00:00 Paula Toth paulatoth@google.com 2020-04-08T17:16:30+00:00 66d00feb186619cc5919a18ab56334558e6bbd45 Summary: Made all header files consistent based of this documentation: https://llvm.org/docs/CodingStandards.html#file-headers. And did the same for all source files top of file comments. Reviewers: sivachandra, abrachet Reviewed By: sivachandra, abrachet Subscribers: MaskRay, tschuett, libc-commits Tags: #libc-project Differential Revision: https://reviews.llvm.org/D77533 
Summary:
Made all header files consistent based of this documentation: https://llvm.org/docs/CodingStandards.html#file-headers.
And did the same for all source files top of file comments.

Reviewers: sivachandra, abrachet

Reviewed By: sivachandra, abrachet

Subscribers: MaskRay, tschuett, libc-commits

Tags: #libc-project

Differential Revision: https://reviews.llvm.org/D77533
[libc] Replace the use of gtest with a new light weight unittest framework. 2020-01-18T00:24:53+00:00 Siva Chandra Reddy sivachandra@google.com 2020-01-10T21:43:20+00:00 c7453fad0625be37f4b885c6cc2341fb12a66395 Header files included wrongly using <...> are now included using the internal path names as the new unittest framework allows us to do so. Reviewers: phosek, abrachet Differential Revision: https://reviews.llvm.org/D72743 
Header files included wrongly using <...> are now included using the
internal path names as the new unittest framework allows us to do so.

Reviewers: phosek, abrachet

Differential Revision: https://reviews.llvm.org/D72743
[libc] Move implementations of strcat and strcpy to the string directory. 2020-01-07T06:20:42+00:00 Siva Chandra Reddy sivachandra@google.com 2020-01-06T18:38:45+00:00 188f72ab20d9523d6ffde8ad8361ecf17bb75946 Summary: Now that tests live in separate top-level directory, keeping the implementations of individual functions in a directory of their own is not meaningful. Hence, this change moves them into the higher level string directory. NFC intended. Reviewers: MaskRay Subscribers: mgorny, tschuett, libc-commits Tags: #libc-project Differential Revision: https://reviews.llvm.org/D72295 
Summary:
Now that tests live in separate top-level directory, keeping the
implementations of individual functions in a directory of their own is
not meaningful. Hence, this change moves them into the higher level
string directory.

NFC intended.

Reviewers: MaskRay

Subscribers: mgorny, tschuett, libc-commits

Tags: #libc-project

Differential Revision: https://reviews.llvm.org/D72295
[libc] Move all tests to a top level `test` directory. 2020-01-06T18:14:43+00:00 Siva Chandra Reddy sivachandra@google.com 2020-01-03T20:00:45+00:00 5b24c088171d3bd7a8ff559c82926e5d4b04f032 A toplevel target, `check-libc` has also been added. Reviewers: abrachet, phosek Tags: #libc-project Differential Revision: https://reviews.llvm.org/D72177 
A toplevel target, `check-libc` has also been added.

Reviewers: abrachet, phosek

Tags: #libc-project

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