search for: dllvm_use_linker

...ng with the following config: cmake -G Ninja ../llvm \ -DLLVM_ENABLE_PROJECTS='clang;compiler-rt' \ -DLLVM_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_buil...

...>> -DLLVM_ENABLE_PROJECTS='clang;compiler-rt' \ >> -DLLVM_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/rel...

cmake -G Ninja -DLLVM_ENABLE_PROJECTS="debuginfo-tests" -DLLVM_USE_LINKER=lld -DCMAKE_BUILD_TYPE="Release" -DLLVM_TARGETS_TO_BUILD=X86 -Wno-dev ../llvm &> ../../cmake.log in cmake.log -- Targeting X86 CMake Error at /home/nnelson/Documents/llvm-project/debuginfo-tests/CMakeLists.txt:30 (message):   Cannot run debuginfo-tests without python 3 instal...

...have the compiler-rt sources in llvm/projects/compiler-rt. > Lastly, can you provide your CMake configuration command line? cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -G Ninja -DCMAKE_CXX_COMPILER=clang++-3.9 -DCMAKE_C_COMPILER=clang-3.9 -DCMAKE_ASM_COMPILER=clang-3.9 -DLLVM_USE_LINKER=gold -DLLVM_USE_SPLIT_DWARF=On -DBUILD_SHARED_LIBS=ON -DLLVM_OPTIMIZED_TABLEGEN=On -DCOMPILER_RT_BUILD_XRAY=On -DLLVM_ENABLE_ASSERTIONS=On -DCOMPILER_RT_INCLUDE_TESTS=On -DLLVM_ENABLE_SPHINX=On -DSPHINX_WARNINGS_AS_ERRORS=On -DCMAKE_CXX_FLAGS="-Wpedantic" -DCMAKE_CXX_COMPILER_LAUNCHER=cca...

...g directory. > Xubuntu 19.04. llvm downloaded from github on 6/18 using instructions from the page you note. > cmake -G Ninja -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra;compiler-rt;debuginfo-tests;libclc;libcxx;libcxxabi;libunwind;lld;lldb;llvm;openmp;parallel-libs;polly;pstl" -DLLVM_USE_LINKER=lld -DCMAKE_BUILD_TYPE="Release" ../llvm > Installed additional packages as needed. > Neil > On 7/5/19 6:46 AM, Joan Lluch via llvm-dev wrote: >> Hi All, >> >> I am looking for the best way to install LLVM+clang, but I do not seem to find a way that works for...

...; > Joan, > > Just completed a good clang compile built from a mostly vanilla Xubuntu 19.04 VM, installed the llvm-needed Ubuntu packages, downloaded a new copy of llvm using the noted llvm install page, configured using > > cmake -G Ninja -DLLVM_ENABLE_PROJECTS="clang" -DLLVM_USE_LINKER=lld -DCMAKE_BUILD_TYPE="Release" -DCMAKE_INSTALL_PREFIX=/home/nnelson/Documents/llvm/install ../llvm &> cmake.log > > which is primarily different from yours where I am using a 'Release' build to avoid the much larger memory and disk usage of a 'Debug' build....

I've started looking at the state of code coverage recently; we figured LLVM itself would be a good test to figure out how mature it is, so I gave it a shot. My experience: 1. You have to specify -DLLVM_USE_LINKER=gold (or maybe lld works; I didn't try). If you link with binutils ld, the program will generate broken profile information. Apparently, the linked binary is missing the __llvm_prf_names section. This took me half a day to figure out. This issue isn't documented anywhere, and the on...

...Joan, > > Just completed a good clang compile built from a mostly vanilla Xubuntu > 19.04 VM, installed the llvm-needed Ubuntu packages, downloaded a new copy > of llvm using the noted llvm install page, configured using > > cmake -G Ninja -DLLVM_ENABLE_PROJECTS="clang" -DLLVM_USE_LINKER=lld > -DCMAKE_BUILD_TYPE="Release" > -DCMAKE_INSTALL_PREFIX=/home/nnelson/Documents/llvm/install ../llvm &> > cmake.log > > which is primarily different from yours where I am using a 'Release' build > to avoid the much larger memory and disk usage of a ...

...Just completed a good clang compile built from a mostly vanilla Xubuntu >> 19.04 VM, installed the llvm-needed Ubuntu packages, downloaded a new copy >> of llvm using the noted llvm install page, configured using >> >> cmake -G Ninja -DLLVM_ENABLE_PROJECTS="clang" -DLLVM_USE_LINKER=lld >> -DCMAKE_BUILD_TYPE="Release" >> -DCMAKE_INSTALL_PREFIX=/home/nnelson/Documents/llvm/install ../llvm &> >> cmake.log >> >> which is primarily different from yours where I am using a 'Release' >> build to avoid the much larger memory...

Hi, I tried to build LLVM 4.0.1 on a Slackware Linux box with 3 GB of RAM using gcc-7.1.0. Near the end of the build process, I hit the following error: [ 89%] Linking CXX shared library ../../lib/libLTO.so collect2: fatal error: ld terminated with signal 9 [Killed] compilation terminated. tools/lto/CMakeFiles/LTO.dir/build.make:269: recipe for target 'lib/libLTO.so.4.0.1' failed

On 6/18/2017 3:51 PM, Vedant Kumar wrote: >> My experience: >> >> 1. You have to specify -DLLVM_USE_LINKER=gold (or maybe lld works; I >> didn't try). If you link with binutils ld, the program will generate >> broken profile information. Apparently, the linked binary is missing >> the __llvm_prf_names section. This took me half a day to figure out. >> This issue isn...

...good clang compile built from a mostly vanilla Xubuntu >>> 19.04 VM, installed the llvm-needed Ubuntu packages, downloaded a new copy >>> of llvm using the noted llvm install page, configured using >>> >>> cmake -G Ninja -DLLVM_ENABLE_PROJECTS="clang" -DLLVM_USE_LINKER=lld >>> -DCMAKE_BUILD_TYPE="Release" >>> -DCMAKE_INSTALL_PREFIX=/home/nnelson/Documents/llvm/install ../llvm &> >>> cmake.log >>> >>> which is primarily different from yours where I am using a 'Release' >>> build to avoi...

I'm trying to do a simple build from the git 8.0.0 sources. The sources seem to build OK but a link step fails from running out of memory. I need some clues how to figure out where the bottleneck might be. The cmake command is: cmake -G Ninja                                          \     -DLLVM_TARGETS_TO_BUILD=X86                         \    

...a good clang compile built from a mostly vanilla Xubuntu 19.04 VM, installed the llvm-needed Ubuntu packages, downloaded a new copy of llvm using the noted llvm install page, configured using >>>>>> >>>>>> cmake -G Ninja -DLLVM_ENABLE_PROJECTS="clang" -DLLVM_USE_LINKER=lld -DCMAKE_BUILD_TYPE="Release" -DCMAKE_INSTALL_PREFIX=/home/nnelson/Documents/llvm/install ../llvm &> cmake.log >>>>>> >>>>>> which is primarily different from yours where I am using a 'Release' build to avoid the much larger memory an...

Johannes, This patch seems to be causing test failures when I just do "ninja check", without running "ninja" or "ninja all" first. $ CC=clang CXX=clang++ cmake -G Ninja ~/git/llvm-project/llvm -DLLVM_USE_LINKER=lld -DLLVM_PARALLEL_LINK_JOBS=4 -DCMAKE_BUILD_TYPE=Release -DLLVM_TARGETS_TO_BUILD=X86 && ninja check [...] FAIL: LLVM :: tools/llvm-config/system-libs.test (32608 of 34640) ******************** TEST 'LLVM :: tools/llvm-config/system-libs.test' FAILED ******************** Script: --...

...rote: > > Johannes, > > > > This patch seems to be causing test failures when I just do "ninja > > check", without running "ninja" or "ninja all" first. > > > > $ CC=clang CXX=clang++ cmake -G Ninja ~/git/llvm-project/llvm > > -DLLVM_USE_LINKER=lld -DLLVM_PARALLEL_LINK_JOBS=4 > > -DCMAKE_BUILD_TYPE=Release -DLLVM_TARGETS_TO_BUILD=X86 && ninja check > > [...] > > FAIL: LLVM :: tools/llvm-config/system-libs.test (32608 of 34640) > > ******************** TEST 'LLVM :: tools/llvm-config/system-libs.test'...

Hi llvm-dev, I have unit tests set up in the XRay implementation (compiler-rt/lib/xray/tests/unit) following the pattern that the TSAN and other sanitiser unit tests. However, I'm running into the following problem: When I make changes to the runtime (in this case, XRay) and do `ninja all check-xray`, it seems that the unit tests don't get re-liked to the new version of the runtime. It

...> This patch seems to be causing test failures when I just do "ninja > > > > check", without running "ninja" or "ninja all" first. > > > > > > > > $ CC=clang CXX=clang++ cmake -G Ninja ~/git/llvm-project/llvm > > > > -DLLVM_USE_LINKER=lld -DLLVM_PARALLEL_LINK_JOBS=4 > > > > -DCMAKE_BUILD_TYPE=Release -DLLVM_TARGETS_TO_BUILD=X86 && ninja check > > > > [...] > > > > FAIL: LLVM :: tools/llvm-config/system-libs.test (32608 of 34640) > > > > ******************** TEST 'LLVM :...

...-DCOMPILER_RT_BUILD_SANITIZERS=on -DCOMPILER_RT_BUILD_XRAY=off \ -DLLVM_ENABLE_PROJECTS="clang;compiler-rt;lld;openmp" \ -DLLVM_ENABLE_ASSERTIONS=on -DLLVM_OPTIMIZED_TABLEGEN=on \ -DLLVM_STATIC_LINK_CXX_STDLIB=on -DLLVM_TARGETS_TO_BUILD="AArch64;X86" \ -DLLVM_USE_LINKER=gold -DLLVM_USE_SANITIZER=Address ../llvm Stage 1 was built from the same source using the same CMake command, without -DLLVM_USE_SANITIZER. CMAKE_C_FLAGS and CMAKE_CXX_FLAGS contained some hardening options like "-fstack-protector-strong -D_FORTIFY_SOURCE=2" which I omitted for brevity....

Hi, Building LLVM with a newer GCC version seems to generate several compiler warnings, some of which look like false positives. For example, the '-Winit-list-lifetime' warning added in GCC9 triggers for one of the constructors for ArrayRef, the one taking an initializer_list. How are false positive warnings dealt with in LLVM in general? It's of course possible to just ignore them