[PATCH] D58184: [scudo][standalone] Introduce platform specific code & mutexes

[Kostya Kortchinsky via Phabricator via llvm-commits]

cryptoad added a comment.

AFAICT, the compilation invocation that is failing should have a `-m32` for it to succeed which is not there. The following succeeds (with the extra -m32):

  .../llvm-build/gcc/bin/clang++ -fPIC -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -std=c++11 -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -fdiagnostics-color -Wall -std=c++11 -Wno-unused-parameter -g  -Wl,-z,defs -Wl,-z,nodelete -shared -Wl,-soname,libRTScudoStandalone.test.i386.so -o lib/libRTScudoStandalone.test.i386.so projects/compiler-rt/lib/scudo/standalone/CMakeFiles/RTScudoStandalone.i386.dir/common.cc.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/RTScudoStandalone.i386.dir/fuchsia.cc.o projects/compiler-rt/lib/scudo/standalone/CMakeFiles/RTScudoStandalone.i386.dir/linux.cc.o  -m32

The -m32 seems to be added to the CMAKE_C_FLAGS variable but is not.
The different between my build that succeeds and this one boils down to -DCMAKE_C_COMPILER=$HOME/llvm-build/gcc/bin/clang vs CC=$HOME/llvm-build/gcc/bin/clang for me.
I am still not fully sure how to get around that.


Repository:
  rCRT Compiler Runtime

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D58184/new/

https://reviews.llvm.org/D58184