search for: dllvm_build_runtime

...nal 2013 Version 12.0.21005.1 REL Microsoft .NET Framework Version 4.6.01055 Installed Version: Professional Here's what it showed during cmake: c:\"Program Files (x86)"\CMake\bin\cmake -G "Visual Studio 12" /m -DLLVM_TARGETS_TO_BUILD:STRING=All" "-DLLVM_BUILD_RUNTIME:BOOL=OFF" "-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY:BOOL=ON" "-DLIBCLANG_BUILD_STATIC=ON" "-DLLVM_USE_MC_TOOLS:STRING=yes" "-DLLVM_ENABLE_PIC:BOOL=ON" "-DLLVM_ENABLE_ASSERTIONS:BOOL=ON" "-DWITH_POLLY:BOOL=OFF" "-DLLVM_BUILD_RUNTIM...

...work > Version 4.6.01055 > > Installed Version: Professional > > > Here's what it showed during cmake: > > c:\"Program Files (x86)"\CMake\bin\cmake -G "Visual Studio 12" /m > -DLLVM_TARGETS_TO_BUILD:STRING=All" "-DLLVM_BUILD_RUNTIME:BOOL=OFF" > "-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY:BOOL=ON" > "-DLIBCLANG_BUILD_STATIC=ON" "-DLLVM_USE_MC_TOOLS:STRING=yes" > "-DLLVM_ENABLE_PIC:BOOL=ON" "-DLLVM_ENABLE_ASSERTIONS:BOOL=ON" > "-DWITH_POLLY:BOOL=OFF...

...VM_TARGETS_TO_BUILD=X86 \ -DCMAKE_EXPORT_COMPILE_COMMANDS=ON \ -DCMAKE_CXX_COMPILER=/path/to/release_build/bin/clang++ \ -DCMAKE_C_COMPILER=/path/to/release_build/bin/clang \ -DLLVM_USE_LINKER=/path/to/release_build/bin/ld.lld \ -DLLVM_CCACHE_BUILD=ON \ -DLLVM_BUILD_INSTRUMENTED=IR \ -DLLVM_BUILD_RUNTIME=No \ -DLLVM_ENABLE_ZLIB=1 \ -DCMAKE_BUILD_TYPE=Release \ -DLLVM_ENABLE_LTO=Thin \ -DCMAKE_RANLIB=/path/to/release_build/bin/llvm-ranlib \ -DCMAKE_AR=/path/to/release_build/bin/llvm-ar I tried this without specifying zlib being enabled, without thinlto, everything I could come up with rea...

Hello, I suspect that r260758 by kparzysz at codeaurora.org broke build the windows bots which are using Visual Studio 2013 or lower. This doc here specifies that the minimum version required is VS-2013: http://llvm.org/docs/GettingStarted.html#host-c-toolchain-both-compiler-and-standard-library I do see that the bots running VS-2014 or higher are green. Can we either revert the said commit or

...MANDS=ON \ >> -DCMAKE_CXX_COMPILER=/path/to/release_build/bin/clang++ \ >> -DCMAKE_C_COMPILER=/path/to/release_build/bin/clang \ >> -DLLVM_USE_LINKER=/path/to/release_build/bin/ld.lld \ >> -DLLVM_CCACHE_BUILD=ON \ >> -DLLVM_BUILD_INSTRUMENTED=IR \ >> -DLLVM_BUILD_RUNTIME=No \ >> -DLLVM_ENABLE_ZLIB=1 \ >> -DCMAKE_BUILD_TYPE=Release \ >> -DLLVM_ENABLE_LTO=Thin \ >> -DCMAKE_RANLIB=/path/to/release_build/bin/llvm-ranlib \ >> -DCMAKE_AR=/path/to/release_build/bin/llvm-ar >> >> I tried this without specifying zlib being...

...bcxxabi. The build compiler is: clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04 The failures show up during "make check-all". My cmake command was: cmake -G 'Unix Makefiles' -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/w/c/org -DLLVM_TARGETS_TO_BUILD:STRING=all -DLLVM_BUILD_RUNTIME:BOOL=ON -DLIBCLANG_BUILD_STATIC=ON -DLLVM_ENABLE_PIC:BOOL=ON -DLLVM_ENABLE_ASSERTIONS:BOOL=ON -DLLVM_INCLUDE_TOOLS:BOOL=ON -DLLVM_LIT_ARGS:STRING="-s -v" -DWITH_POLLY:BOOL=ON -DLINK_POLLY_INTO_TOOLS:BOOL=ON -DCMAKE_C_COMPILER=/w/c/clang+llvm-3.7.0-x86_64-linux-gnu-u...

Hello List, I'm currently writing my own little optimization pass (on LLVM 6.0) and considered it a neat idea to fuzz it using llvm-opt-fuzzer, which in theory should be a ready-made tool for such jobs as far as I can tell, potentially helping me to find UB and Address issues in my pass. So I went ahead and followed the instructions in the build manual [1] to build LLVM's llvm-opt-fuzzer

After re-cmaking and rebuilding everything from scratch, I'm seeing failures in MCJIT. It this something known or expected? I build LLVM/clang with pre-packaged clang-3.7.0, with "-stdlib=libc++". Example failure: /w/bld/org/./bin/lli -remote-mcjit -mcjit-remote-process=/w/bld/org/./bin/lli-child-target /w/src/llvm.org/test/ExecutionEngine/MCJIT/remote/eh.ll -- Exit Code: