[libc-commits] [PATCH] D146184: [libc] Inherit integration test dependencies from the startup target
Joseph Huber via Phabricator via libc-commits
libc-commits at lists.llvm.org
Thu Mar 16 05:33:45 PDT 2023
This revision was landed with ongoing or failed builds.
This revision was automatically updated to reflect the committed changes.
Closed by commit rGf62523032d1d: [libc] Inherit integration test dependencies from the startup target (authored by jhuber6).
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D146184/new/
https://reviews.llvm.org/D146184
Files:
libc/cmake/modules/LLVMLibCTestRules.cmake
Index: libc/cmake/modules/LLVMLibCTestRules.cmake
===================================================================
--- libc/cmake/modules/LLVMLibCTestRules.cmake
+++ libc/cmake/modules/LLVMLibCTestRules.cmake
@@ -439,15 +439,9 @@
get_fq_deps_list(fq_deps_list ${INTEGRATION_TEST_DEPENDS})
list(APPEND fq_deps_list
- # All integration tests setup TLS area and the main thread's self object.
- # So, we need to link in the threads implementation. Likewise, the startup
- # code also has to run init_array callbacks which potentially register
- # their own atexit callbacks. So, link in exit and atexit also with all
- # integration tests.
- libc.src.__support.threads.thread
- libc.src.stdlib.atexit
- libc.src.stdlib.exit
- libc.src.unistd.environ
+ # All integration tests need to inherit the same dependencies as the
+ # startup code.
+ ${INTEGRATION_TEST_STARTUP}
# We always add the memory functions objects. This is because the
# compiler's codegen can emit calls to the C memory functions.
libc.src.string.bcmp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D146184.505780.patch
Type: text/x-patch
Size: 1108 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/libc-commits/attachments/20230316/5f615ce0/attachment.bin>
More information about the libc-commits
mailing list