search for: llvm_enable_libcxxabi

...scription of each option in the CMakeLists.txt :) llvm/trunk/CMakeLists.txt option(LLVM_ENABLE_MODULES "Compile with C++ modules enabled." OFF) option(LLVM_ENABLE_CXX1Y "Compile with C++1y enabled." OFF) option(LLVM_ENABLE_LIBCXX "Use libc++ if available." OFF) option(LLVM_ENABLE_LIBCXXABI "Use libc++abi when using libc++." OFF) option(LLVM_ENABLE_PEDANTIC "Compile with pedantic enabled." ON) option(LLVM_ENABLE_WERROR "Fail and stop if a warning is triggered." OFF) Kind Regards Martell On Tue, Jul 28, 2015 at 12:30 PM, Martell Malone <martellmalone...

Hi Michael, I am wondering about the meaning of the cmake flags LLVM_ENABLE_LIBCXX and > LLVM_ENABLE_LIBCXXABI. Are they used to indicate that if the C/C++ compiler > for building LLVM is clang, and if this clang has support for libc++ with > libc++Abi, that both lib++ and libc++abi should be used (instead of linking > to the default, which at least on Linux is libstdc++)? Yes that is actually wh...

Hi, I am wondering about the meaning of the cmake flags LLVM_ENABLE_LIBCXX and LLVM_ENABLE_LIBCXXABI. Are they used to indicate that if the C/C++ compiler for building LLVM is clang, and if this clang has support for libc++ with libc++Abi, that both lib++ and libc++abi should be used (instead of linking to the default, which at least on Linux is libstdc++)? If not, what is the canonical way of bui...

> > That's how I read it. :) :) Adding a little to the topic what criteria would we need to make a target use compiler-rt and libc++ as the default in the clang driver. I have successfully built a standalone clang toolchain with mingw-w64 without using gcc or binutils. Currently I locally patch this to be the default. On Tue, Jul 28, 2015 at 2:33 PM, Renato Golin <renato.golin at

Wouldn’t it it be possible to add a flag like the one used in the OpenMP subproject? There they default to linking to the non-functional libgomp (as far as I understand it), and if people want to use the actual libomp runtime, they have to specify -fopenmp=libomp when compiling/linking a program. At the same time, it is possible to use the libomp runtime library by default by specifying

On 28 July 2015 at 12:10, Schlottke-Lakemper, Michael <m.schlottke-lakemper at aia.rwth-aachen.de> wrote: > I am wondering about the meaning of the cmake flags LLVM_ENABLE_LIBCXX and LLVM_ENABLE_LIBCXXABI. Are they used to indicate that if the C/C++ compiler for building LLVM is clang, and if this clang has support for libc++ with libc++Abi, that both lib++ and libc++abi should be used (instead of linking to the default, which at least on Linux is libstdc++)? If not, what is the canonical way of bui...

On 28 July 2015 at 14:44, Martell Malone <martellmalone at gmail.com> wrote: > Adding a little to the topic what criteria would we need to make a target > use compiler-rt and libc++ as the default in the clang driver. > I have successfully built a standalone clang toolchain with mingw-w64 > without using gcc or binutils. There was another discussion with David Chisnall, where he

...n Tue, Jul 28, 2015 at 1:06 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 28 July 2015 at 12:10, Schlottke-Lakemper, Michael > <m.schlottke-lakemper at aia.rwth-aachen.de> wrote: > > I am wondering about the meaning of the cmake flags LLVM_ENABLE_LIBCXX > and LLVM_ENABLE_LIBCXXABI. Are they used to indicate that if the C/C++ > compiler for building LLVM is clang, and if this clang has support for > libc++ with libc++Abi, that both lib++ and libc++abi should be used > (instead of linking to the default, which at least on Linux is libstdc++)? > If not, what is the...

On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote: [ brutal-snip ] ... > [ TODO#S: Before doing a 2nd build (and in a 3rd run using more > optimized binaries) ] > > How do I anable LTO via CMAKE? > > > LLVM_ENALBLE_LTO=On > [ v4 of my build-script attached ] Hi Chris, thanks for the response! That seems to work (see below). $ cd

Trying to run a self host "ninja check-clang" with ASan enabled I hit a /lot/ of errors like this (strangely I hit none of these in check-llvm, only in check-clang): Any ideas? ==10525==ERROR: AddressSanitizer failed to deallocate 0x10800 (67584) bytes at address 0x631000014800 ==10525==AddressSanitizer CHECK failed:

...OFF //Enable Exception handling LLVM_ENABLE_EH:BOOL=ON //Enable expensive checks LLVM_ENABLE_EXPENSIVE_CHECKS:BOOL=OFF //Use libffi to call external functions from the interpreter LLVM_ENABLE_FFI:BOOL=OFF //Use libc++ if available. LLVM_ENABLE_LIBCXX:BOOL=OFF //Use libc++abi when using libc++. LLVM_ENABLE_LIBCXXABI:BOOL=OFF //Use libedit if available. LLVM_ENABLE_LIBEDIT:BOOL=ON //Use lld as C and C++ linker. LLVM_ENABLE_LLD:BOOL=OFF //Compile with -fmodules-local-submodule-visibility. LLVM_ENABLE_LOCAL_SUBMODULE_VISIBILITY:BOOL=ON //Enable link-time optimization LLVM_ENABLE_LTO:BOOL=OFF //Compile with C...