search for: cmake_linker

...="2" ##COMPILE_JOBS=$(($(getconf _NPROCESSORS_ONLN)+1)) LINK_JOBS="1" JOBS_CMAKE_OPTS="-DLLVM_PARALLEL_COMPILE_JOBS=$COMPILE_JOBS -DLLVM_PARALLEL_LINK_JOBS=$LINK_JOBS" # Cmake linker options (here: Use binutils-gold to speedup build) LINKER="/usr/bin/ld.gold" CMAKE_LINKER="$LINKER" CMAKE_LINKER_OPTS="-DCMAKE_LINKER=$CMAKE_LINKER" # CMake Generators CMAKE_GENERATORS="Ninja" GENERATORS_CMAKE_OPTS="-G $CMAKE_GENERATORS" # CMake configure settings PREFIX_CMAKE_OPTS="-DCMAKE_INSTALL_PREFIX=$PREFIX" OPTIMIZED_CMAKE_OPTS=&q...

...; > Where does lld-link2 get chosen? CMake doesn't have code for that > name so something else in your project must be specifying it somehow. Yes, the simplest way to reproduce the problem is to run mkdir build cd build cmake ..\llvm -G Ninja -DCMAKE_CXX_CREATE_STATIC_LIBRARY=foobar -DCMAKE_LINKER=c:\users\espindola\llvm\inst\bin\lld-link2 and then ninja -v lib\LLVMSupport.lib I would expect it to fail trying to run foobar, but it works by running lld-link2 Cheers, Rafael

> The Modules/Platform/Windows-MSVC.cmake module unconditionally > sets CMAKE_CXX_CREATE_STATIC_LIBRARY and uses CMAKE_LINKER. > As mentioned earlier the CMAKE_<LANG>_CREATE_STATIC_LIBRARY > and similar variables are internal implementation details > that are not meant to be set by users or project code. That > is why the above works only on certain platforms. > > Will thin archive support be dist...

...on the blog-texts. It might be that a CLANG generated with LTO/PGO speeds up the build. Can you confirm this? Can you confirm binutils-gold speed up the build? Has LLVM an own linker? Can be used? Speedup the build? Yesterday night I loooked through available CMAKE/LLVM variables... ### GOLD # CMAKE_LINKER:FILEPATH=/usr/bin/ld # GOLD_EXECUTABLE:FILEPATH=/usr/bin/ld.gold # LLVM_TOOL_GOLD_BUILD:BOOL=ON ### OPTLEVEL # CMAKE_ASM_FLAGS_RELEASE:STRING=-O3 -DNDEBUG # CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG # CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG ### LTO # LLVM_TOOL_LLVM_LTO_BUILD:BOOL=ON # LLVM_TOOL...

.../llvm -DCMAKE_BUILD_TYPE=Release -DLLVM_OPTIMIZED_TABLEGEN=true -DLLVM_EXTERNAL_LLD_SOURCE_DIR=f:/svn/lld -DLLVM_TOOL_LLD_BUILD=true -DLLVM_ENABLE_LLD=true -DCMAKE_C_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" -DCMAKE_CXX_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" -DCMAKE_LINKER="C:/Program Files/LLVM/bin/lld-link.exe" -DLLVM_ENABLE_PDB=true It will be faster to compile. The setup I use is the above Ninja cmd-line for compiling optimized builds; and in addition, I keep the Visual Studio generator, as you do, but only for having a .sln to debug. It is a bit annoy...

.../llvm -DCMAKE_BUILD_TYPE=Release -DLLVM_OPTIMIZED_TABLEGEN=true -DLLVM_EXTERNAL_LLD_SOURCE_DIR=f:/svn/lld -DLLVM_TOOL_LLD_BUILD=true -DLLVM_ENABLE_LLD=true -DCMAKE_C_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" -DCMAKE_CXX_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" -DCMAKE_LINKER="C:/Program Files/LLVM/bin/lld-link.exe" -DLLVM_ENABLE_PDB=true >> >> It will be faster to compile. The setup I use is the above Ninja cmd-line for compiling optimized builds; and in addition, I keep the Visual Studio generator, as you do, but only for having a .sln to debug....

.../llvm -DCMAKE_BUILD_TYPE=Release -DLLVM_OPTIMIZED_TABLEGEN=true -DLLVM_EXTERNAL_LLD_SOURCE_DIR=f:/svn/lld -DLLVM_TOOL_LLD_BUILD=true -DLLVM_ENABLE_LLD=true -DCMAKE_C_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" -DCMAKE_CXX_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" -DCMAKE_LINKER="C:/Program Files/LLVM/bin/lld-link.exe" -DLLVM_ENABLE_PDB=true > >> > >> It will be faster to compile. The setup I use is the above Ninja cmd-line for compiling optimized builds; and in addition, I keep the Visual Studio generator, as you do, but only for having a .sln...

.../llvm -DCMAKE_BUILD_TYPE=Release -DLLVM_OPTIMIZED_TABLEGEN=true -DLLVM_EXTERNAL_LLD_SOURCE_DIR=f:/svn/lld -DLLVM_TOOL_LLD_BUILD=true -DLLVM_ENABLE_LLD=true -DCMAKE_C_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" -DCMAKE_CXX_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" -DCMAKE_LINKER="C:/Program Files/LLVM/bin/lld-link.exe" -DLLVM_ENABLE_PDB=true >> >> It will be faster to compile. The setup I use is the above Ninja cmd-line for compiling optimized builds; and in addition, I keep the Visual Studio generator, as you do, but only for having a .sln to debug....

...NAL_LLD_SOURCE_DIR=f:/svn/lld > > >> -DLLVM_TOOL_LLD_BUILD=true -DLLVM_ENABLE_LLD=true > > >> -DCMAKE_C_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" > > >> -DCMAKE_CXX_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" > > >> -DCMAKE_LINKER="C:/Program Files/LLVM/bin/lld-link.exe" > > >> -DLLVM_ENABLE_PDB=true > > >> > > >> It will be faster to compile. The setup I use is the above Ninja cmd-line for compiling optimized builds; and in addition, I keep the Visual Studio generator, as you do...

That's good news. For having debug info, you could try adding /Z7 on the cmake cmd-line, such as -DCMAKE_CXX_FLAGS="/Z7". Or use the 'RelWithDebInfo' target instead of 'Release' and add -DCMAKE_CXX_FLAGS="/Ob2" (because that target uses /Ob1 as a default). Can you please send a patch on Phabricator if you fix the LLVM_ENABLE_PDB issue with Clang? The goal

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

...> > >> -DLLVM_TOOL_LLD_BUILD=true -DLLVM_ENABLE_LLD=true > > > > >> -DCMAKE_C_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" > > > > >> -DCMAKE_CXX_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" > > > > >> -DCMAKE_LINKER="C:/Program Files/LLVM/bin/lld-link.exe" > > > > >> -DLLVM_ENABLE_PDB=true > > > > >> > > > > >> It will be faster to compile. The setup I use is the above Ninja > cmd-line for compiling optimized builds; and in addition, I keep the...

...:/svn/lld > > > >> -DLLVM_TOOL_LLD_BUILD=true -DLLVM_ENABLE_LLD=true > > > >> -DCMAKE_C_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" > > > >> -DCMAKE_CXX_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" > > > >> -DCMAKE_LINKER="C:/Program Files/LLVM/bin/lld-link.exe" > > > >> -DLLVM_ENABLE_PDB=true > > > >> > > > >> It will be faster to compile. The setup I use is the above Ninja cmd-line for compiling optimized builds; and in addition, I keep the Visual Studio gener...

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:

> On Mar 2, 2016, at 4:22 PM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > > I got some more inspirations on how to speedup my build and integrated > the URLs into my scripts (attached). > > For example to use GOLD as linker or to use '-O3' OptLevel maybe in > combination with LTO and PGO (using '-O3 -flto -fprofile-use'). LTO *will* slow down

...directories. CMAKE_INSTALL_PREFIX:PATH=/usr/local //system admin executables (sbin) CMAKE_INSTALL_SBINDIR:PATH=sbin //modifiable architecture-independent data (com) CMAKE_INSTALL_SHAREDSTATEDIR:PATH=com //read-only single-machine data (etc) CMAKE_INSTALL_SYSCONFDIR:PATH=etc //Path to a program. CMAKE_LINKER:FILEPATH=/usr/local/google/home/blaikie/install/bin/ld //Program used to build from build.ninja files. CMAKE_MAKE_PROGRAM:FILEPATH=/usr/local/google/home/blaikie/install/bin/ninja //Flags used by the linker during the creation of modules. CMAKE_MODULE_LINKER_FLAGS:STRING= //Flags used by the lin...

> On Jul 23, 2016, at 1:53 PM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > On Sat, Jul 23, 2016 at 7:48 PM, Piotr Padlewski <prazek at google.com <mailto:prazek at google.com>> wrote: >> How big is your project? >> LTO eats RAM even faster than chrome. For example linking clang with LTO >>