The integration tests require the C memory functions as the compiler may
emit calls to them directly. The tests normally use the __internal__
variant that is built for testing, but these memory functions were
linked directly to preserve the entrypoint. Instead, we forward delcare
the internal versions and map the entrypoints to them manually inside
the integration test. This allows us to use the internal versions of
these files like the rest of the test objects.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
libc/cmake/modules/LLVMLibCTestRules.cmake | ||
---|---|---|
450–452 | if these appends are both done unconditionally to the same list they can probably be combined. |
libc/cmake/modules/LLVMLibCTestRules.cmake | ||
---|---|---|
450–452 | Soon I'm going to try to add the GPU integration test support, which will be different. I think we should make the former inherit all the dependencies from the STARTUP argument. What do you think @sivachandra? |
libc/cmake/modules/LLVMLibCTestRules.cmake | ||
---|---|---|
450–452 | Yes, that would be good. You can still combine them into a single APPEND operation and add some comment about why the memory functions are being added - a modified version of what was present on lines 477 to 480. | |
libc/test/IntegrationTest/test.cpp | ||
29 | Nit: Empty lines between the definitions to improve readability. |
Merging the dependency list and addressing comments. I'll try to remove the other dependencies by picking them up from the startup in a later patch.
if these appends are both done unconditionally to the same list they can probably be combined.