diff options
author | Simi Pallipurath <simi.pallipurath@arm.com> | 2025-05-08 12:41:07 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2025-05-08 12:41:07 +0100 |
commit | d1783406720dc0fd30fec7bb354c37ec307c6e10 (patch) | |
tree | 9996576a6ccd341a727664d6919464d58fae8fad /lldb/source/Commands/CommandObjectSource.cpp | |
parent | 52b345d036677e6377ea5e2022a1b6bd403ed91e (diff) | |
download | llvm-d1783406720dc0fd30fec7bb354c37ec307c6e10.zip llvm-d1783406720dc0fd30fec7bb354c37ec307c6e10.tar.gz llvm-d1783406720dc0fd30fec7bb354c37ec307c6e10.tar.bz2 |
[ARM][Compiler-RT] Add optional exclusion of libc provided ARM AEABI builtins from compiler-rt. (#137952)
This patch introduces a new optional CMake flag:
COMPILER_RT_EXCLUDE_LIBC_PROVIDED_ARM_AEABI_BUILTINS
When enabled, this flag excludes the following ARM AEABI memory function
implementations from the compiler-rt build:
__aeabi_memcmp
__aeabi_memset
__aeabi_memcpy
__aeabi_memmove
These functions are already provided by standard C libraries like glibc,
newlib, and picolibc, so excluding them avoids duplicate symbol
definitions and reduces unnecessary code duplication.
Note:
- libgcc does not define the __aeabi_* functions that overlap with those
provided by the C library. Enabling this option makes compiler-rt behave
consistently with libgcc.
- This prevents duplicate symbol errors when linking, particularly in
bare-metal configurations where compiler-rt is linked first.
- This flag is OFF by default, meaning all AEABI memory builtins will
still be built unless explicitly excluded.
This change is useful for environments where libc provides runtime
routines, supporting more minimal, conflict free builds.
Diffstat (limited to 'lldb/source/Commands/CommandObjectSource.cpp')
0 files changed, 0 insertions, 0 deletions