similar to: Cannot compile LLVM suite with clang+lld

You also need -DLIBUNWIND_USE_COMPILER_RT=ON -DLIBCXXABI_USE_LLVM_UNWINDER=ON. This is because you set -DLIBCXXABI_USE_COMPILER_RT=ON so libc++abi.so is no longer being linked agains libgcc_s.so which is where the unwinder otherwise comes from. On Sun, May 6, 2018 at 4:05 AM via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I try to compile LLVM, clang, lld and libcxx together in one

Hello, I'm trying to create a pure LLVM toolchain (that will not depend on GNU and produce GNU-free code too) on a musl based distribution. For now, I use gcc to bootstrap and build all LLVM components. I do it individually because I was running out of space and memory trying to build all using LLVM_ENABLE_PROJECTS. Also, I don't want to create a all-in-one package. Then, once

Folks, I am using a two-stagesimple build like this one: make -G Ninja -DCLANG_ENABLE_BOOTSTRAP=ON ../src ninja stage2-check-all Stage 1 gets built, and when looking at rules.ninja in the stage2-bins I see: rule CXX_COMPILER_AnalysisTests depfile = $DEP_FILE deps = gcc command = <stage1 build dir>./bin/clang++ $DEFINES $INCLUDES $FLAGS -MMD -MT $out -MF $DEP_FILE -o $out -c $in

Hello everyone, Since MLIR landed today. I'm trying to build it using cmake ../llvm/ -DCMAKE_BUILD_TYPE=RELEASE -DLLVM_TARGETS_TO_BUILD=X86 -DLLVM_ALL_PROJECTS="clang;lld;lldb;mlir" -DBUILD_SHARED_LIBS=ON -DCLANG_DEFAULT_LINKER:STRING=lld and also by adding -DLLVM_ALL_PROJECTS. It's giving this compilation error -- Building CXX object

Are you using static linking, -DBUILD_SHARED_LIBS, or -DLLVM_LINK_LLVM_DYLIB? On Tue, Jan 8, 2019 at 7:21 AM David Greene via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Rui Ueyama <ruiu at google.com> writes: > > > I cannot reproduce this error, but this could be real. > > > > David, is this reproducible every time or is this flaky? > > It's

Thus wrote David Demelier via llvm-dev: > Also you will need to add more options to the components. See for example: > > LIBCXX_CXX_ABI=libcxxabi > LIBCXX_USE_COMPILER_RT=On > LIBCXXABI_USE_LLVM_UNWINDER=On > LIBCXXABI_USE_COMPILER_RT=On > LIBCXX_HAS_GCC_S_LIB=Off > LIBUNWIND_USE_COMPILER_RT=On > > And as mentioned above > > CLANG_DEFAULT_CXX_STDLIB=libc++

These errors seem pretty pervasive for me on a clean build. It appears that it arises because when tablegen'd headers are included in a .h file, every place where that .h file is used needs a dependency on the corresponding IncGen targets. This seems broken in the short term and unmaintainable in the long term. There really needs to be a way of automatically generating the right

I can build llvm and associated tools in a 1 shot go using gcc and g++ but trying to use only gcc and bootstrap clang to build and link with libc++ and libc++abi on the second phase of the build, the compilation fails I have svn cloned LLVM CLANG CLANG_XTRA_TOOLS LLD LLDB POLLY COMPILER_RT OPENMP LIBCXX LIBCXXABI cmake command below cmake -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=OFF

Hi folks! I'm trying to get rid of any dependency on libgcc*, but without success so far. The following commands were executed on a freshliy installed and updated Ubuntu 16.04 LTS: === snip === sudo apt-get install build-essential libffi-dev cmake # see aptget.txt for packages installed sudo mv /usr/local /usr/local.orig git clone https://github.com/llvm/llvm-project.git cd llvm-project; git

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

Just to follow-up, I'm now encountering this as well. I'm doing this on Linux. It seems that when linking with the most-recently built clang, the unit tests are taking a while to complete. It's notably not using more than 1 thread, and if using `lld` I would have expected the linker to still be running in parallel. I'm doing this on a debug build, so that might help narrow it

Hi, A few tests seem broken for a long time, some for more than a month. Would it possible for respective owners to take a look please? I'm at checkout 133a7e631cee97965e310f0d110739217427fd3d, compiling on Windows 10. These tests fail with Visual Studio 2019: Failing Tests (7): Clang Tools :: clang-tidy/checkers/cert-mem57-cpp-cpp17.cpp Clang Tools ::

On 20 July 2015 at 10:53, Brad King <brad.king at kitware.com> wrote: > On 07/20/2015 10:48 AM, Rafael Espíndola wrote: >>>> Setting CMAKE_CXX_CREATE_STATIC_LIBRARY works on OS X and linux, but >>>> on windows I still see a call to "lld-link2 /lib..." when >>>> CMAKE_CXX_CREATE_STATIC_LIBRARY is set to use llvm-lib. >> >> I was

Hi! I'm trying to build a fast Clang for myself to use for debug builds on Clang itself, but I've been struggling for a very long time on it. Could you please help? I've been following this guide: https://llvm.org/docs/HowToBuildWithPGO.html I've quickly learned that its outdated, because the script it talks about doesn't work with the monorepo layout at all, but in any

Yes, that was it! Now that I took a closer look, the guide also states that I should use the stage2 build. Silly me. Thanks! On Tue, 3 Sep 2019 at 19:31, David Blaikie <dblaikie at gmail.com> wrote: > I /guess/ you actually want /path/to/release_build/llvm-profdata because > the profiles are generated from binaries compiled with the release build, > so it's the release build

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:

The configuration we’re mentioning is a 2-stage bootstrap: You need first to build without LTO your own clang, and then use it for the LTO build. — Mehid > On Sep 20, 2016, at 10:17 AM, Michael Kruse <llvmdev at meinersbur.de> wrote: > > I am the author of Polly's/ISL's platform tests and could reproduce > the problem on my system with this error message: > >

Can you please try using Ninja instead? cmake -G Ninja f:/svn/llvm -DCMAKE_BUILD_TYPE=Release -DLLVM_OPTIMIZED_TABLEGEN=true -DLLVM_EXTERNAL_LLD_SOURCE_DIR=f:/svn/lld -DLLVM_TOOL_LLD_BUILD=true -DLLVM_ENABLE_LLD=true -DCMAKE_C_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" -DCMAKE_CXX_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" -DCMAKE_LINKER="C:/Program

So, for this test case: extern "C" void shouldBeUnconditional(); extern "C" void shouldBeConditional(); extern "C" void otherCall(); void testFn(bool Bool1, bool Bool2) { Bool1 |= Bool2; shouldBeUnconditional(); if (Bool1) shouldBeConditional(); if (Bool2) { otherCall(); if (Bool1) otherCall(); } } MSVC generates this buggy asm: $ cl -c

I think its a huge bug that it doesn't raise any errors or warnings about it. But I will open a ticket on cmake, they should be using clang-cl.exe and lld-link.exe if T="llvm" probably set host to 64 bit as well. On Mon, Feb 25, 2019 at 3:34 PM Zachary Turner <zturner at google.com> wrote: > > I don’t think changing the compiler or linker is supported with the vs