search for: dllvm_enable_assert

...; Chandler, >> >> I may be doing this wrong, but I'm getting a weird error in building LLVM >> with Clang via CMake. >> >> On x86_64: >> $ CC=clang CXX=clang++ cmake -G Ninja ../../src/llvm >> -DCMAKE_BUILD_TYPE=Release -DLLVM_BUILD_TESTS=True >> -DLLVM_ENABLE_ASSERTIONS=True >> >> On ARM: >> $ CC=clang CXX=clang++ cmake -G Ninja ../src/ -DCMAKE_BUILD_TYPE=Release >> -DCMAKE_INSTALL_PREFIX=../install -DCMAKE_C_FLAGS=-mcpu=cortex-a15 >> -DCMAKE_CXX_FLAGS=-mcpu=cortex-a15 -DLLVM_TARGETS_TO_BUILD=ARM >> -DLLVM_BUILD_TESTS=True -...

Chandler, I may be doing this wrong, but I'm getting a weird error in building LLVM with Clang via CMake. On x86_64: $ CC=clang CXX=clang++ cmake -G Ninja ../../src/llvm -DCMAKE_BUILD_TYPE=Release -DLLVM_BUILD_TESTS=True -DLLVM_ENABLE_ASSERTIONS=True On ARM: $ CC=clang CXX=clang++ cmake -G Ninja ../src/ -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=../install -DCMAKE_C_FLAGS=-mcpu=cortex-a15 -DCMAKE_CXX_FLAGS=-mcpu=cortex-a15 -DLLVM_TARGETS_TO_BUILD=ARM -DLLVM_BUILD_TESTS=True -DLLVM_ENABLE_ASSERTIONS=True Warning: CMake Warning...

...st slow? I'm reasonably certain I'm compiling LLVM in optimized mode, but for reference, this is my build line:     cmake .. -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_EH=ON -DLLVM_ENABLE_RTTI=ON -DLLVM_REQUIRES_RTTI=ON -DLLVM_ENABLE_CXX1Y=ON -DLLVM_LINK_LLVM_DYLIB=ON -DLLVM_ENABLE_FFI=ON -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_OPTIMIZED_TABLEGEN=ON -DCMAKE_INSTALL_PREFIX="/opt/llvm/install" The overall time split, from valgrind, between shared libraries in my code is:     80.48%, libLLVM-6.0.so     8.83% libc-2.23.so     2.34% libleaf_lang.so (my front-end) -- edA-qa mort-ora-y http://mort...

...certain I'm compiling LLVM in optimized mode, but for > reference, this is my build line: > >     cmake .. -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_EH=ON > -DLLVM_ENABLE_RTTI=ON -DLLVM_REQUIRES_RTTI=ON -DLLVM_ENABLE_CXX1Y=ON > -DLLVM_LINK_LLVM_DYLIB=ON -DLLVM_ENABLE_FFI=ON > -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_OPTIMIZED_TABLEGEN=ON > -DCMAKE_INSTALL_PREFIX="/opt/llvm/install" You're building LLVM with assertions enabled (-DLLVM_ENABLE_ASSERTIONS=ON). Some of those are fairly expensive... - Andres

...t; I still don't see these errors locally. Can you try with an autoconf-based > build and see if they're somehow related to (triggered by) the way that > cmake builds LLVM? > > On the same machine autoconf build is fine where as cmake has failures, reproduced simply with cmake -DLLVM_ENABLE_ASSERTIONS=ON -DCMAKE_BUILD_TYPE=Release .. make -j10 make check-all -j10 Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140401/8e83a943/attachment.html>

...t, but there have been a few other changes in the last week or so that may be related). I'm building with a fresh top-of-tree clang and setting -DLLVM_USE_SANITIZER=Address and -DLLVM_USE_SANITIZE_COVERAGE=On, which was working before: % cmake -GNinja \ -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=On \ -DLLVM_ENABLE_WERROR=On \ -DLLVM_USE_SANITIZER=Address -DLLVM_USE_SANITIZE_COVERAGE=On \ -DCMAKE_C_COMPILER=$HOME/llvm-lkgc/bin/clang \ $HOME/code/llvm-src But when I run any of the fuzzers, it looks like the sanitizer coverage hasn't been set u...

...ang/CMakeLists.txt by changing add_definitions( -D_GNU_SOURCE ) to add_definitions( -D_GNU_SOURCE -U_DEBUG -DNDEBUG ) which disables assertions for clang. Then build LLVM+Clang using the option for enabling assertions: mkdir mybuilddir && cd mybuilddir cmake -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=ON path/to/llvm/src (In the cmake build, assertions are disabled by default in Release mode)

Hi, I'd like to build llvm with assertions enabled, but build clang with assertions disabled. In other words, I'd like lvm in Release+Asserts mode, but clang in Release mode. Is it possible to do this with one top level configure/make command? If not, any idea how much work would it be to add this feature to llvm? I'm not very familiar with llvm's build system. Thanks!

...error is at the end of this log: http://104.154.46.123:8010/builders/win-64-trunk/builds/75/steps/Build%20LLVM%20Release/logs/stdio My build procedure looks like this: cmake -DCMAKE_INSTALL_PREFIX=../llvm-install -DLLVM_ENABLE_TERMINFO=OFF -DLLVM_TARGETS_TO_BUILD=X86;ARM;NVPTX;AArch64;Mips -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_BUILD_32_BITS=OFF -DCMAKE_BUILD_TYPE=Release../llvm/ -G 'Visual Studio 12 Win64' MSBuild.exe /m /t:Build /p:Configuration="Debug" .\ALL_BUILD.vcxproj MSBuild.exe /m /t:Build /p:Configuration="Release" .\ALL_BUILD.vcxproj Suggestions appreciated. All oth...

...fuse-ld=gold"\ -DCMAKE_BUILD_TYPE=RelWithDebInfo ' \ -DCMAKE_C_FLAGS="-O2 -g" \ -DCMAKE_CXX_FLAGS="-O2 -g" \ -DENABLE_LINKER_BUILD_ID=ON \ -DLLVM_ENABLE_ASSERTIONS=ON \ -DLLVM_ENABLE_PIC=ON \ -DLLVM_BINUTILS_INCDIR=/usr/include \ -DLLVM_TARGETS_TO_BUILD=host \ -DLLVM_TARGET_ARCH=host \ -DLLVM_LIBDIR_SUFFIX=64 \...

...ndle everything correctly, calloc() must be > "statically" intercepted before __asan_init is called from the CRT > (hence before "dynamic" interceptors are set up). > > Can you please compare what happens in your build configuration compared to: > $ cmake -GNinja -DLLVM_ENABLE_ASSERTIONS=ON -DCMAKE_BUILD_TYPE=Release > -DLLVM_TARGETS_TO_BUILD=X86 .. && ninja > instead? Do I need something special to support ninja? E:\llvm\compiler-rt-ninja>cmake -GNinja -DLLVM_ENABLE_ASSERTIONS=ON -DCMAKE_BUIL D_TYPE=Release -DLLVM_TARGETS_TO_BUILD=X86 ..\compiler-rt &&am...

...r so that may be related). >> >> I'm building with a fresh top-of-tree clang and setting >> -DLLVM_USE_SANITIZER=Address and -DLLVM_USE_SANITIZE_COVERAGE=On, which >> was working before: >> >> % cmake -GNinja \ >> -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=On \ >> -DLLVM_ENABLE_WERROR=On \ >> -DLLVM_USE_SANITIZER=Address -DLLVM_USE_SANITIZE_COVERAGE=On \ >> -DCMAKE_C_COMPILER=$HOME/llvm-lkgc/bin/clang \ >> $HOME/code/llvm-src >> >> But when I run any of the fuzzers, it looks...

Posting to the list first, rather than filing a bug because I'm not sure this is still an intended configuration: With LLVM configured as: CXX=clang++ CC=clang cmake ../llvm/ \ -DCMAKE_BUILD_TYPE=Release \ -DCMAKE_INSTALL_PREFIX=~/install/llvm-master/ \ -DLLVM_TARGETS_TO_BUILD=host \ -DLLVM_ENABLE_ASSERTIONS=true \ -DLLVM_ENABLE_LIBCXX=yes \ -DLLVM_ENABLE_LIBCXXABI=yes The check-all target is failing to compile the interception tests: /home/sdowney/bld/llvm-master/llvm/projects/compiler-rt/lib/interception/tests/interception_linux_test.cc:26:18: error: redefinition of 'isdigit' INTERCEPTOR...

FTR, I've disabled libcxx checkout on that particular bot <http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fuzzer> to make it green. The problem remains, of course. :( On Sun, Dec 11, 2016 at 7:23 AM, James Knight <jyknight at google.com> wrote: > On Dec 11, 2016, at 3:33 AM, Eric Fiselier via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > So it

...ests fail since end of November-December. The MachO tests fail since about the beginning of December. The Polly test fails since a few days ago. (see below for more info) I'm using the following cmake cmd-line: cmake -GNinja %ROOT%/llvm -DCMAKE_BUILD_TYPE=Release -DLLVM_OPTIMIZED_TABLEGEN=ON -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_ENABLE_LIBXML2=OFF -DCMAKE_C_COMPILER="%VS2019%/bin/HostX64/x64/cl.EXE" -DCMAKE_CXX_COMPILER="%VS2019%/bin/HostX64/x64/cl.EXE" -DCMAKE_LINKER="%VS2019%/bin/HostX64/x64/link.EXE" -DLLVM_ENABLE_PROJECTS="llvm;clang;lld;clang-tools-extra;compiler-rt;mli...

...be >>> "statically" intercepted before __asan_init is called from the CRT >>> (hence before "dynamic" interceptors are set up). >>> >>> Can you please compare what happens in your build configuration compared to: >>> $ cmake -GNinja -DLLVM_ENABLE_ASSERTIONS=ON -DCMAKE_BUILD_TYPE=Release >>> -DLLVM_TARGETS_TO_BUILD=X86 .. && ninja >>> instead? >> >> Do I need something special to support ninja? > > Put it onto your PATH? > e.g. you can > $ svn export http://src.chromium.org/svn/trunk/tools/depot_too...

...setFunctionAttributes(llvm::StringRef, llvm::StringRef, llvm::TargetOptions const&, llvm::Module&, bool)' collect2: error: ld returned 1 exit status This is my CMake command line: cmake -G Ninja $LLVM_SRC -DCMAKE_BUILD_TYPE=Debug -DLLVM_BUILD_TESTS=False -DLLVM_INCLUDE_EXAMPLES=False -DLLVM_ENABLE_ASSERTIONS=True -DBUILD_SHARED_LIBS=True -DLLVM_TARGETS_TO_BUILD="ARM;X86;AArch64" -DPYTHON_EXECUTABLE=/usr/bin/python2 Static object compilation is unaffected. Any ideas? cheers, --renato

On Dec 11, 2016, at 3:33 AM, Eric Fiselier via llvm-dev <llvm-dev at lists.llvm.org> wrote: > So it seems that libatomic went missing between build #1379 and #1380, so I don't think this is related to the -std=c++11 failure. Instead it seems likely that the compile test for -std=c++11 is failing due to mis-configuring -latomic. > > Can you confirm the bot has libatomic

...-DCMAKE_BUILD_TYPE=RelWithDebInfo ' \ >> -DCMAKE_C_FLAGS="-O2 -g" \ >> -DCMAKE_CXX_FLAGS="-O2 -g" \ >> -DENABLE_LINKER_BUILD_ID=ON \ >> -DLLVM_ENABLE_ASSERTIONS=ON \ >> -DLLVM_ENABLE_PIC=ON \ >> -DLLVM_BINUTILS_INCDIR=/usr/include \ >> -DLLVM_TARGETS_TO_BUILD=host \ >> -DLLVM_TARGET_ARCH=host \ >> -D...

...on, I figured I'd try building using CMake. I checked out llvm, cfe and lldb from the SVN server, and followed the basic build instructions. cmake -DBUILD_SHARED_LIBS=OFF -DCMAKE_INSTALL_PREFIX=/tools/llvm/svn_head -DLLVM_TARGETS_TO_BUILD="X86;CppBackend" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=ON ../llvm Everything worked well, and in the end I got the following shared libraries: /tools/llvm/svn_head/lib/BugpointPasses.so /tools/llvm/svn_head/lib/libclang.so /tools/llvm/svn_head/lib/libclang.so.3.9 /tools/llvm/svn_head/lib/liblldb.so /tools/llvm/svn_head/lib/liblldb.so.3.9.0 /tools...