search for: llvm_enable_werror

...the C++ compiler will display warnings and terminate? I broke the build yesterday because I had not seen a warning that then showed up in the build. I have these two options set in CMakeCache.txt: //Enable compiler warnings. LLVM_ENABLE_WARNINGS:BOOL=ON //Fail and stop if a warning is triggered. LLVM_ENABLE_WERROR:BOOL=ON

...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 at gmail.com> wrote: > Hi Michael, > > I am wondering about the meaning of the cmake flags LLVM_ENABLE_LIBCXX and >> LLVM_ENABLE_LI...

While doing a make on the recently checkout version: I got the following errors: [ 68%] Built target dd [ 68%] Built target compiler-rt-headers [ 68%] Building C object projects/compiler-rt/lib/builtins/CMakeFiles/clang_rt.builtins-x86_64.dir/x86_64/floatdidf.c.o In file included from /home/tthtlc/llvm/llvm/projects/compiler-rt/lib/builtins/x86_64/floatdidf.c:9:0:

...Werror] > #endif // defined(_MSC_VER) && !defined(__clang__) > > and > > error: (this will be reported only once per input file) [-Werror] > cc1: all warnings being treated as errors > > So, did you happen to have generated your make files using CMake > passing -DLLVM_ENABLE_WERROR=ON ? > > My reasoning is as follows (but please do correct me if I'm wrong > somewhere): When generating your make file using cmake, since by > default LLVM_ENABLE_PEDANTIC is set to ON, the above warning gets > triggered (cf. the description of "pedantic" at > https...

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

...NTIME_OUTPUT_INTDIR}/llvm-config > > + -DLLVM_LIBRARY_OUTPUT_INTDIR=${LLVM_LIBRARY_OUTPUT_INTDIR} > > + -DLLVM_RUNTIME_OUTPUT_INTDIR=${LLVM_RUNTIME_OUTPUT_INTDIR} > > + -DLLVM_LIBDIR_SUFFIX=${LLVM_LIBDIR_SUFFIX} > > + -DLLVM_ENABLE_WERROR=${LLVM_ENABLE_WERROR} > > + -DPACKAGE_VERSION=${PACKAGE_VERSION} > > + -DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE} > > + -DCMAKE_MAKE_PROGRAM=${CMAKE_MAKE_PROGRAM} > > How did you decide which variables need to be passed through like thi...

...>>> > + -DLLVM_LIBRARY_OUTPUT_INTDIR=${LLVM_LIBRARY_OUTPUT_INTDIR} >>> > + -DLLVM_RUNTIME_OUTPUT_INTDIR=${LLVM_RUNTIME_OUTPUT_INTDIR} >>> > + -DLLVM_LIBDIR_SUFFIX=${LLVM_LIBDIR_SUFFIX} >>> > + -DLLVM_ENABLE_WERROR=${LLVM_ENABLE_WERROR} >>> > + -DPACKAGE_VERSION=${PACKAGE_VERSION} >>> > + -DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE} >>> > + -DCMAKE_MAKE_PROGRAM=${CMAKE_MAKE_PROGRAM} >>> >>> How did you decide which vari...

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

...-DLLVM_LIBRARY_OUTPUT_INTDIR=${LLVM_LIBRARY_OUTPUT_INTDIR} >>>>> > + -DLLVM_RUNTIME_OUTPUT_INTDIR=${LLVM_RUNTIME_OUTPUT_INTDIR} >>>>> > + -DLLVM_LIBDIR_SUFFIX=${LLVM_LIBDIR_SUFFIX} >>>>> > + -DLLVM_ENABLE_WERROR=${LLVM_ENABLE_WERROR} >>>>> > + -DPACKAGE_VERSION=${PACKAGE_VERSION} >>>>> > + -DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE} >>>>> > + -DCMAKE_MAKE_PROGRAM=${CMAKE_MAKE_PROGRAM} >>>>> >>&g...

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:

...//Use Sphinx to generate llvm documentation. LLVM_ENABLE_SPHINX:BOOL=OFF //Use terminfo database if available. LLVM_ENABLE_TERMINFO:BOOL=ON //Use threads if available. LLVM_ENABLE_THREADS:BOOL=ON //Enable compiler warnings. LLVM_ENABLE_WARNINGS:BOOL=ON //Fail and stop if a warning is triggered. LLVM_ENABLE_WERROR:BOOL=ON //Use zlib for compression/decompression if available. LLVM_ENABLE_ZLIB:BOOL=ON //Semicolon-separated list of experimental targets to build. LLVM_EXPERIMENTAL_TARGETS_TO_BUILD:STRING= //Export symbols from LLVM tools so that plugins can import them LLVM_EXPORT_SYMBOLS_FOR_PLUGINS:BOOL=OF...