search for: enableabibreakingchecks

Hi, when using the "Debug" build of LLVM 8.0 my application which uses the LLVM builder and MCJIT components fails at startup with: symbol lookup error: ./main: undefined symbol: _ZN4llvm23EnableABIBreakingChecksE (unmangled: llvm::EnableABIBreakingChecks) The application works fine with the "Release" build of LLVM 8.0! (Right now, I need the Debug build for access to dump() ). The application works also fine with both the Debug or Release build with LLVM 6.0. Looking for differences regards...

...The symbol name would be different if the ABI break is >> enabled or not. > > Can it be made into a link-time check instead? I'm imagining something like: I’d love to, but didn’t find a universal solution unfortunately :( > #if LLVM_ENABLE_ABI_BREAKING_CHECKS > extern int EnableABIBreakingChecks; > __attribute__((weak)) int *VerifyEnableABIBreakingChecks = &EnableABIBreakingChecks; > #else > extern int DisableABIBreakingChecks; > __attribute__((weak)) int *VerifyDisableABIBreakingChecks = &VDisableABIBreakingChecks; > #endif > > in llvm-config.h.cmake, an...

Hi all, An issue that come up from time to time and has cost hours for debug for many of us and users of LLVM is that an assert build isn’t ABI compatible with a release build. The CMake flags that controls this behavior is LLVM_ABI_BREAKING_CHECKS ( LLVM_ABI_BREAKING_CHECKS:STRING Used to decide if LLVM should be built with ABI breaking checks or not. Allowed values are WITH_ASSERTS (default),