search for: dllvm_enable_lld

Hello, I have a working GCC toolchain and wanted to use LLVM tooling instead. Following the instructions on the website I set up my build directory and have lld as an internal project under tools/. I'd like to make use of lld in stage 2 of the build and thought -DLLVM_ENABLE_LLD was the correct option to pass. However, adding this options makes the configure step fail, complaining that the compiler (GCC) does not support -fuse-ld=lld. Is it possible, and if yes - how, to set up a 2-stages build to compile LLVM, Clang and LLD so that in stage 2, only LLVM tools are part of...

...-DCMAKE_LINKER=lld -DCMAKE_LINK_EXECUTABLE="/usr/bin/ld.lld" -DCMAKE_AR="/usr/bin/llvm-ar" -DCMAKE_AS="/usr/bin/llvm-as" -DCLANG_DEFAULT_LINKER=lld -DCLANG_DEFAULT_RTLIB=compiler-rt -DCLANG_ENABLE_BOOTSTRAP=ON -DLIBCXX_USE_COMPILER_RT=ON -DLIBCXXABI_USE_COMPILER_RT=ON -DLLVM_ENABLE_LLD=ON -DLLVM_ENABLE_LIBCXX=ON However, the build fails with (many of those error messages): [1274/2712] Linking CXX shared library lib/libc++abi.so.1.0 FAILED: lib/libc++abi.so.1. /usr/bin/ld.lld: error: undefined symbol: _Unwind_Resume >>> referenced by ld-temp.o >>>...

..._container.h:83: > Error: attempt to self move assign. > > Objects involved in the operation: > sequence "this" @ 0x0x7fe3b3070468 { > } > The command I've been using to configure it is > cmake ../llvm -G Ninja \ > -DCMAKE_BUILD_TYPE=Debug \ > -DLLVM_ENABLE_LLD=On \ > -DLLVM_ENABLE_EXPENSIVE_CHECKS=On > Removing the -DLLVM_ENABLE_EXPENSIVE_CHECKS=On allows it to build. Is there something wrong with the version on libstdc++ on my system? (Debian testing) This was happening on revision 5857bf5d1e5a5ffe5ae51a38514ee55495c0cc69 ----------------------...

.... Cheers,Jonas Am Freitag, den 06.01.2017, 13:44 +0900 schrieb Rui Ueyama: > Hi Hahnfeld, > I just compiled with LLVM_LINK_LLVM_DYLIB enabled [1] and build lld with `ninja lld`. It built fine. What am I missing? > > [1] $ cmake -GNinja -DCMAKE_BUILD_TYPE=Debug -DLLVM_ENABLE_THREADS=On -DLLVM_ENABLE_LLD=true -DLLVM_LINK_LLVM_DYLIB=true -DLLVM_ENABLE_PROJECTS='clang;lld' ../llvm-project/llvm > > On Wed, Jan 4, 2017 at 10:31 PM, Hahnfeld, Jonas via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi all, > > > > > > > > I recently gave LLD a try...

...even a line of code. Please use it! Using LLD to link LLVM/clang/etc is easy. You need to check out the LLD repository just like you probably already did for clang, build it, and then install it. LLD will be installed as ld.lld (and it won't be used by default.) After that, re-run cmake with -DLLVM_ENABLE_LLD=On along with your usual options so that LLD will be used to build LLVM. For the details of the build process, please see http://lld.llvm.org/#build. Thanks, Rui -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachment...

...900 schrieb Rui Ueyama: >> >> Hi Hahnfeld, >> >> I just compiled with LLVM_LINK_LLVM_DYLIB enabled [1] and build lld with >> `ninja lld`. It built fine. What am I missing? >> >> [1] $ cmake -GNinja -DCMAKE_BUILD_TYPE=Debug -DLLVM_ENABLE_THREADS=On >> -DLLVM_ENABLE_LLD=true -DLLVM_LINK_LLVM_DYLIB=true >> -DLLVM_ENABLE_PROJECTS='clang;lld' ../llvm-project/llvm >> >> On Wed, Jan 4, 2017 at 10:31 PM, Hahnfeld, Jonas via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >> >> Hi all, >> >> I recently gave LL...

...v to see invocation) ninja: build stopped: subcommand failed. CMake will not be able to correctly generate this project. Call Stack (most recent call first): CMakeLists.txt:49 (project) My configuration is shown below: cmake -G Ninja -DBUILD_SHARED_LIBS=ON -DLLVM_PARALLEL_LINK_JOBS=2 -DLLVM_ENABLE_LLD=ON -DLLVM_ENABLE_LIBCXX=OFF -DCMAKE_BUILD_TYPE=Release -DGCC_INSTALL_PREFIX=/pathto/gcc-7.5.0/ -DLIBOMPTARGET_ENABLE_DEBUG=ON -DCMAKE_INSTALL_PREFIX=$HOME/opt/clang/${today} -DCMAKE_C_COMPILER=clang -DCMAKE_C_FLAGS="" -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_CXX_FLAGS="" -DLLVM_ENAB...

...LE="/usr/bin/ld.lld" > -DCMAKE_AR="/usr/bin/llvm-ar" > -DCMAKE_AS="/usr/bin/llvm-as" > -DCLANG_DEFAULT_LINKER=lld > -DCLANG_DEFAULT_RTLIB=compiler-rt > -DCLANG_ENABLE_BOOTSTRAP=ON > -DLIBCXX_USE_COMPILER_RT=ON > -DLIBCXXABI_USE_COMPILER_RT=ON > -DLLVM_ENABLE_LLD=ON > -DLLVM_ENABLE_LIBCXX=ON > > However, the build fails with (many of those error messages): > > [1274/2712] Linking CXX shared library lib/libc++abi.so.1.0 > FAILED: lib/libc++abi.so.1. > /usr/bin/ld.lld: error: undefined symbol: _Unwind_Resume > >>> referenced b...

...;s the CMake command I'm using: ==== cmake -GNinja -DCMAKE_C_COMPILER=$HOME/xray/llvm-project-build/bin/clang -DCMAKE_CXX_COMPILER=$HOME/xray/llvm-project-build/bin/clang++ -DCMAKE_BUILD_TYPE=Debug -DLLVM_OPTIMIZED_TABLEGEN=On -DLLVM_ENABLE_ASSERTIONS=On -DLLVM_USE_SANITIZER=MemoryWithOrigins -DLLVM_ENABLE_LLD=On -DLLVM_INCLUDE_TESTS=On -DCMAKE_CXX_FLAGS=-stdlib=libc++ -DCMAKE_LINK_FLAGS=-stdlib=libc++ ../llvm-project/llvm ==== And I'm running the tests like so: ==== ninja check-llvm ==== I'm doing this with the monorepo, if that's relevant. Help? -- Dean

Hi all, I recently gave LLD a try and it definitely works fine. However one cannot build it together with LLVM_LINK_LLVM_DYLIB: ELF/Driver.cpp and ELF/DriverUtils.cpp pull in llvm/Support/CommandLine.h which defines the command line options so these global variables end up in libLLVM-4.0svn.so via liblldELF. If this shared library is then linked into bin/lld or bin/opt one gets errors because of

...; >> Using LLD to link LLVM/clang/etc is easy. You need to check out the LLD >> repository just like you probably already did for clang, build it, and then >> install it. LLD will be installed as ld.lld (and it won't be used by >> default.) After that, re-run cmake with -DLLVM_ENABLE_LLD=On along with >> your usual options so that LLD will be used to build LLVM. >> >> For the details of the build process, please see >> http://lld.llvm.org/#build. >> >> Thanks, >> Rui >> _______________________________________________ >> LLVM Dev...

...; cmake -GNinja -DCMAKE_C_COMPILER=$HOME/xray/llvm-project-build/bin/clang > > -DCMAKE_CXX_COMPILER=$HOME/xray/llvm-project-build/bin/clang++ > > -DCMAKE_BUILD_TYPE=Debug -DLLVM_OPTIMIZED_TABLEGEN=On > > -DLLVM_ENABLE_ASSERTIONS=On -DLLVM_USE_SANITIZER=MemoryWithOrigins > > -DLLVM_ENABLE_LLD=On -DLLVM_INCLUDE_TESTS=On > > -DCMAKE_CXX_FLAGS=-stdlib=libc++ -DCMAKE_LINK_FLAGS=-stdlib=libc++ > > ../llvm-project/llvm > > ==== > > > > And I'm running the tests like so: > > > > ==== > > ninja check-llvm > > ==== > > > > I...

where should the file build_llvm_package.bat be placed and how should the build_llvm_package.bat be called? or is there a another way to do a two stage build of the llvm project on windows starting with using visual studio 2017 community. -------------- next part -------------- An HTML attachment was scrubbed... URL:

...AKE_C_COMPILER=$HOME/xray/llvm-project-build/bin/clang > > > -DCMAKE_CXX_COMPILER=$HOME/xray/llvm-project-build/bin/clang++ > > > -DCMAKE_BUILD_TYPE=Debug -DLLVM_OPTIMIZED_TABLEGEN=On > > > -DLLVM_ENABLE_ASSERTIONS=On -DLLVM_USE_SANITIZER=MemoryWithOrigins > > > -DLLVM_ENABLE_LLD=On -DLLVM_INCLUDE_TESTS=On > > > -DCMAKE_CXX_FLAGS=-stdlib=libc++ -DCMAKE_LINK_FLAGS=-stdlib=libc++ > > > ../llvm-project/llvm > > > ==== > > > > > > And I'm running the tests like so: > > > > > > ==== > > > ninja check-llv...

...; >> Using LLD to link LLVM/clang/etc is easy. You need to check out the LLD >> repository just like you probably already did for clang, build it, and then >> install it. LLD will be installed as ld.lld (and it won't be used by >> default.) After that, re-run cmake with -DLLVM_ENABLE_LLD=On along with >> your usual options so that LLD will be used to build LLVM. >> >> For the details of the build process, please see >> http://lld.llvm.org/#build. >> >> Thanks, >> Rui >> _______________________________________________ >> LLVM Dev...

...C_COMPILER="%LLVM%/bin/clang-cl.EXE" -DCMAKE_CXX_COMPILER="%LLVM%/bin/clang-cl.EXE" -DCMAKE_LINKER="%LLVM%/bin/lld-link.EXE" -DLLVM_ENABLE_PROJECTS="llvm;clang;lld;clang-tools-extra;compiler-rt;mlir;polly" -DLLVM_ENABLE_PDB=ON -DLLVM_POLLY_LINK_INTO_TOOLS=ON -DLLVM_ENABLE_LLD=ON Thanks in advance! Alex. ________________________________ The clang-tidy cert-mem57 tests seem to be related to varying messages (warning|error) being emitted. All three MachO/gen-dwarf test are crashing at about the same place: Stack dump: 0. Program arguments: d:\llvm-project\buildni...

Hi LLVM developers, llc -march=mips -debug-only=isel was able to work in Nov 8 2017 https://reviews.llvm.org/D39723 But it doesn't work now: $ clang --version LLVM China clang version 6.0.0 (git at github.com:llvm-mirror/clang.git 9b7b03045ee9b5622028537266aafeb9ea218ac1) (git at github.com:llvm-mirror/llvm.git 3a26601a88394c02603b8756527c55df9ab94d78) (based on LLVM 6.0.0svn) Target:

hello, I am trying to build LLVM with default options. I am getting the following error message after make. [100%] Building C object tools/llvm-c-test/CMakeFiles/llvm-c-test.dir/metadata.c.o [100%] Building C object tools/llvm-c-test/CMakeFiles/llvm-c-test.dir/module.c.o [100%] Building C object tools/llvm-c-test/CMakeFiles/llvm-c-test.dir/object.c.o [100%] Building C object

On 28 Oct 2016, at 18:38, Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > GCC uses bfd by default, LLVM uses LLD. If you want to change, use -fuse-ld. GCC doesn’t use BFD by default, it uses /usr/bin/ld (or ${PREFIX}/bin/ld). If that is a symlink to ld.bfd, ld.gold, Apple ld64, or ld.lld, it will use whichever. I think it would be very confusing for clang to use a

...sertions anymore? That said our upstream buildbots infra seems to have explicit defaults: https://github.com/llvm/llvm-zorg/blob/master/zorg/buildbot/builders/UnifiedTreeBuilder.py#L125-L127 For LLD, I don't think we have auto-detection, but I'd be on-board with auto-detecting it and have -DLLVM_ENABLE_LLD default to the auto-detection when empty. But that's another topic... -- Mehdi On Tue, Nov 17, 2020 at 5:50 PM David Blaikie via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: Yeah, that's one I'd be in favor of fixing, if it's still t...