search for: dllvm_parallel_link_job

...=ON \ -DLLVM_ENABLE_LIBCXX=ON \ -DLLVM_ENABLE_RTTI=ON \ -DLLVM_ENABLE_THREADS=ON \ -DLLVM_ENABLE_ZLIB=ON \ -DLLVM_INCLUDE_EXAMPLES=ON \ -DLLVM_INCLUDE_UTILS=ON \ -DLLVM_OPTIMIZED_TABLEGEN=ON \ -DLLVM_PARALLEL_COMPILE_JOBS=15 \ -DLLVM_PARALLEL_LINK_JOBS=15 \ -DLLVM_TARGETS_TO_BUILD="X86" \ -DLLVM_TARGETS_WITH_JIT="X86" Any suggestions? Thank you in advance. -H

> On Sep 16, 2016, at 4:46 PM, Carsten Mattner <carstenmattner at gmail.com> wrote: > > On Sat, Sep 17, 2016 at 12:48 AM, Teresa Johnson <tejohnson at google.com <mailto:tejohnson at google.com>> wrote: >> >> On Fri, Sep 16, 2016 at 2:54 PM, Carsten Mattner via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> >>> On Fri, Sep 16,

...iled with exit code 1 (use -v to see invocation) ninja: build stopped: subcommand failed. CMake will not be able to correctly generate this project. Call Stack (most recent call first): CMakeLists.txt:49 (project) My configuration is shown below: cmake -G Ninja -DBUILD_SHARED_LIBS=ON -DLLVM_PARALLEL_LINK_JOBS=2 -DLLVM_ENABLE_LLD=ON -DLLVM_ENABLE_LIBCXX=OFF -DCMAKE_BUILD_TYPE=Release -DGCC_INSTALL_PREFIX=/pathto/gcc-7.5.0/ -DLIBOMPTARGET_ENABLE_DEBUG=ON -DCMAKE_INSTALL_PREFIX=$HOME/opt/clang/${today} -DCMAKE_C_COMPILER=clang -DCMAKE_C_FLAGS="" -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_CXX_FLAGS=&qu...

>are you setting the optimized tablegen option? LLVM_OPTIMIZED_TABLEGEN is not active - i will try that >In addition, make sure you have plenty of memory i've got only Intel Core 2 Quad CPU Q8300/2.50Ghz and 8GB RAM for testing not much cpu power AND memory Am 19.09.2018 um 11:31 schrieb James Henderson: > Regarding the Debug build taking hours, are you setting the optimized

...;configure and make" to "cmake" build-system and > wanted to speedup my build. > > In my build-script I use... > > CMAKE_JOBS="1" > ##CMAKE_JOBS=$(($(getconf _NPROCESSORS_ONLN)+1)) > JOBS_CMAKE_OPTS="-DLLVM_PARALLEL_COMPILE_JOBS=$CMAKE_JOBS > -DLLVM_PARALLEL_LINK_JOBS=$CMAKE_JOBS" > > [1] says in "LLVM-specific variables" section... > > *** LLVM_PARALLEL_COMPILE_JOBS:STRING > > Define the maximum number of concurrent compilation jobs. > > *** LLVM_PARALLEL_LINK_JOBS:STRING > > Define the maximum number of concur...

...inLTO will work, or is that a build requirement for > bootstrapping llvm in ThinLTO mode? > > Yeah, perhaps this is working somehow anyway. > > Try to build llvm-tblgen, you’ll know quite quickly :) > > > Also, you should limit the number of parallel link jobs: cmake > -DLLVM_PARALLEL_LINK_JOBS=1 > And use ninja if you don’t already: cmake -GNinja > Yes and to add on - the ThinLTO backend by default will kick off std::thread::hardware_concurrency # of threads, which I'm finding is too much for machines with hyperthreading. If that ends up being an issue I can give you a work...

...y than those that don't, and also the clang projects were the worst culprits. On Wed, 19 Sep 2018 at 20:40, Bruce Hoult via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > With debug builds and gnu ld some of the links take up to 9 or 10 GB of RAM, so with only 8 GB you'd want -DLLVM_PARALLEL_LINK_JOBS=1 and even then still be swapping. > > The OS X linker uses far less RAM, and I'm told gold is better too, so maybe there's also no problem on Windows. Or not as much of one. I think I'd use -DLLVM_PARALLEL_LINK_JOBS=1 *anyway* with only 8 GB system RAM. > > On Wed, Sep 19,...

...d >>> wanted to speedup my build. >>> >>> In my build-script I use... >>> >>> CMAKE_JOBS="1" >>> ##CMAKE_JOBS=$(($(getconf _NPROCESSORS_ONLN)+1)) >>> JOBS_CMAKE_OPTS="-DLLVM_PARALLEL_COMPILE_JOBS=$CMAKE_JOBS >>> -DLLVM_PARALLEL_LINK_JOBS=$CMAKE_JOBS" >>> >>> [1] says in "LLVM-specific variables" section... >>> >>> *** LLVM_PARALLEL_COMPILE_JOBS:STRING >>> >>> Define the maximum number of concurrent compilation jobs. >>> >>> *** LLVM_PARALLEL_LIN...

...quot;cmake" build-system and >> wanted to speedup my build. >> >> In my build-script I use... >> >> CMAKE_JOBS="1" >> ##CMAKE_JOBS=$(($(getconf _NPROCESSORS_ONLN)+1)) >> JOBS_CMAKE_OPTS="-DLLVM_PARALLEL_COMPILE_JOBS=$CMAKE_JOBS >> -DLLVM_PARALLEL_LINK_JOBS=$CMAKE_JOBS" >> >> [1] says in "LLVM-specific variables" section... >> >> *** LLVM_PARALLEL_COMPILE_JOBS:STRING >> >> Define the maximum number of concurrent compilation jobs. >> >> *** LLVM_PARALLEL_LINK_JOBS:STRING >> >>...

...=ON \ -DLLVM_ENABLE_LIBCXX=ON \ -DLLVM_ENABLE_RTTI=ON \ -DLLVM_ENABLE_THREADS=ON \ -DLLVM_ENABLE_ZLIB=ON \ -DLLVM_INCLUDE_EXAMPLES=ON \ -DLLVM_INCLUDE_UTILS=ON \ -DLLVM_OPTIMIZED_TABLEGEN=ON \ -DLLVM_PARALLEL_COMPILE_JOBS=15 \ -DLLVM_PARALLEL_LINK_JOBS=15 \ -DLLVM_TARGETS_TO_BUILD="X86" \ -DLLVM_TARGETS_WITH_JIT="X86" Any suggestions? Thank you in advance. -H _______________________________________________ LLVM Developers mailing list llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org> http:...

...pect. > > I would have expected more aggressive pruning or at least not an > increase, though I don't know if it can be caused by > -DBUILD_SHARED_LIBS=OFF. BUILD_SHARED_LIBS is a non-sense from a performance point of view. It is really not advised to use this. > > FYI, -DLLVM_PARALLEL_LINK_JOBS=1 didn't seem to make any difference, > seeing how each LD stop was using all available cores. It only helps limiting oversubscribing the number of cores, and reduces the peak memory for the link. — Mehdi

...svn/llvm-project/lldb/trunk lldb svn co https://github.com/clang-ykt/openmp libomptarget cd ../.. rm -r build mkdir build cd build cmake -DCMAKE_INSTALL_PREFIX:PATH=/usr/local/llvm-trunk \ -DCMAKE_BUILD_TYPE:STRING="Release" \ -DLLVM_PARALLEL_COMPILE_JOBS:STRING="4" \ -DLLVM_PARALLEL_LINK_JOBS:STRING="4" \ -DLLVM_TARGETS_TO_BUILD:STRING="NVPTX;X86" \ -DLLVM_ENABLE_SPHINX:BOOL=ON \ -DSPHINX_OUTPUT_MAN:BOOL=ON \ -DCMAKE_C_COMPILER:STRING="/usr/local/gcc-5.3.0/bin/gcc" \ -DCMAKE_C_FLAGS:STRING="-m64 -I/usr/local/valgrind/include" \...

Hi, On a 1296-core Intel machine with 376 GB, setting -DLLVM_PARALLEL_LINK_JOB=1 does not help (switching back to ld scales) see: [5085/5201] Linking CXX executable bin/clang-11 FAILED: bin/clang-11 : && /home/usr4/c74014i/opt/clang/current/bin/clang++ -stdlib=libc++ -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextr...

Hi, I switched from "configure and make" to "cmake" build-system and wanted to speedup my build. In my build-script I use... CMAKE_JOBS="1" ##CMAKE_JOBS=$(($(getconf _NPROCESSORS_ONLN)+1)) JOBS_CMAKE_OPTS="-DLLVM_PARALLEL_COMPILE_JOBS=$CMAKE_JOBS -DLLVM_PARALLEL_LINK_JOBS=$CMAKE_JOBS" [1] says in "LLVM-specific variables" section... *** LLVM_PARALLEL_COMPILE_JOBS:STRING Define the maximum number of concurrent compilation jobs. *** LLVM_PARALLEL_LINK_JOBS:STRING Define the maximum number of concurrent link jobs. ...whereas my configure-log says....

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: -- : 'RUN: at line 1';...

[Sorry about the crosspost. Since this is a clang build question but the build is invoked from the top-level LLVM directory I'm not sure where the question should go.] I've got a clang build against libstdc++ on Linux but I would really like one built against libc++/libc++abi. In other words I'd like to rebuild clang/llvm with clang using libc++ and libc++abi on Linux. I looked at

Hi,It's first time to post question on community, so I'm not sure this is right way to ask. I'm hoping that someone can help me figure out how to speed up compilation. I'm working on LLVM 4.0 and modifying clang for my own purpose. It seems like after LLVM switches its compilation framework to cmake, the compile time is largely increased. It took almost over an hour even though I

I just built a stage-1 compiler from the 3.9 release bits and built the lldb from head sources which worked fine. Let me try again using 3.9 build compiler to build 3.9 bits. Teresa On Tue, Sep 27, 2016 at 2:55 PM, Teresa Johnson <tejohnson at google.com> wrote: > > > On Tue, Sep 27, 2016, 2:38 PM Carsten Mattner <carstenmattner at gmail.com> > wrote: > >> On

...es, > > > > 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 **********...

...vailable (online) CPUs +1 or set values explicitly # NOTE-3: For fast and safe linking use bintils-gold and LINK_JOBS="1" COMPILE_JOBS="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 $C...