search for: compressbound

Not really, as well as some sensitivity to the input data overall performance of the link with compression will depend on how this is implemented in lld - how is it parallelized? How is it chunked? Is it effectively pipelined with IO? Or, I wouldn't feel comfortable being able to make a recommendation to our end-users on whether to use this option or not based on my existing extensive

...ENS_9allocatorIcEEEaSERKS5_ 0000000000000000 DF *UND* 0000000000000024 GLIBC_2.2.5 sigemptyset 0000000000000000 DF *UND* 0000000000000150 GLIBC_2.2.5 fcntl 0000000000000000 DF *UND* 000000000000004a Base halfdelay 0000000000000000 DF *UND* 0000000000000014 ZLIB_1.2.0 compressBound 0000000000000000 DO *UND* 0000000000000001 Base _ZSt7nothrow 0000000000000000 DF *UND* 0000000000000197 GLIBC_2.2.5 memmove 0000000000000000 DF *UND* 000000000000058e Base _ZNSt3__16__sortIRNS_6__lessImmEEPmEEvT0_S5_T_ 0000000000000000 DF *UND* 0000000000000005...

Hello, I update my building scripts to build LLVM 4.0 RC1 (with clang, lldb, libc++, libc++abi, lld) on CentOS 6 and I got a lot of undefined symbols during linking LLDB. I'm using clang-3.9 and this configuration: -DLLVM_TARGETS_TO_BUILD="X86" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++