search for: llvm_parallel_xxx_job

...ater. > -- > Job pooling is only available with Ninja generators and CMake 3.0 and > later. > > My cmake-version is... > > $ cmake --version > cmake version 2.8.12.2 > > So, I need Ninja *and* CMake >= v3.0 (or is the right CMake version > sufficient) to use LLVM_PARALLEL_XXX_JOBS? Yes. When you run ninja without any argument you have parallelism by default. This options can control the default number of jobs for ninja. Also, especially when doing LTO, you may want to limit the number of link jobs independently from the number of compile job, which is again a facility tha...

...; later. >>>> >>>> My cmake-version is... >>>> >>>> $ cmake --version >>>> cmake version 2.8.12.2 >>>> >>>> So, I need Ninja *and* CMake >= v3.0 (or is the right CMake version >>>> sufficient) to use LLVM_PARALLEL_XXX_JOBS? >>> >>> Yes. When you run ninja without any argument you have parallelism by default. This options can control the default number of jobs for ninja. >>> Also, especially when doing LTO, you may want to limit the number of link jobs independently from the number of compi...

...rs and CMake 3.0 and >>> later. >>> >>> My cmake-version is... >>> >>> $ cmake --version >>> cmake version 2.8.12.2 >>> >>> So, I need Ninja *and* CMake >= v3.0 (or is the right CMake version >>> sufficient) to use LLVM_PARALLEL_XXX_JOBS? >> >> Yes. When you run ninja without any argument you have parallelism by default. This options can control the default number of jobs for ninja. >> Also, especially when doing LTO, you may want to limit the number of link jobs independently from the number of compile job, whic...

> Which combination of cmake/ninja versions are you using (latest are > v3.4.3 and v1.6.0)? > With this combination I could reduce build-time down from approx. 3h down to 01h20m. $ egrep -i 'jobs|ninja' llvm-build/CMakeCache.txt //Program used to build from build.ninja files. CMAKE_MAKE_PROGRAM:FILEPATH=/opt/cmake/bin/ninja //Define the maximum number of concurrent compilation

...s only available with Ninja generators and CMake 3.0 and >> later. >> >> My cmake-version is... >> >> $ cmake --version >> cmake version 2.8.12.2 >> >> So, I need Ninja *and* CMake >= v3.0 (or is the right CMake version >> sufficient) to use LLVM_PARALLEL_XXX_JOBS? > > Yes. When you run ninja without any argument you have parallelism by default. This options can control the default number of jobs for ninja. > Also, especially when doing LTO, you may want to limit the number of link jobs independently from the number of compile job, which is again a...

...available with Ninja generators and CMake 3.0 and later. -- Job pooling is only available with Ninja generators and CMake 3.0 and later. My cmake-version is... $ cmake --version cmake version 2.8.12.2 So, I need Ninja *and* CMake >= v3.0 (or is the right CMake version sufficient) to use LLVM_PARALLEL_XXX_JOBS? If this is a fact, can you please adjust the information in [1]? Do I have other options to speedup my build? ( For testing RCs I tend to use slow build - one single (c)make job. ) My build-script and configure-log are attached. Thanks. Regards, - Sedat - [1] http://llvm.org/docs/CMake.html...

> On Mar 1, 2016, at 9:57 AM, Chris Bieneman <cbieneman at apple.com> wrote: > > There are a few notes I'd like to add to this thread. > > (1) we have a number of places throughout out CMake build where we use features from newer CMakes gated by version checks. Most of these features are performance or usability related. None of them are correctness. Using the latest

On Thu, Mar 17, 2016 at 11:45 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > On Thu, Mar 17, 2016 at 10:05 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> 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 >>>

For faster builds and rebuilds you should definitely read: https://blogs.s-osg.org/an-introduction-to-accelerating-your-build-with-clang/ https://blogs.s-osg.org/a-conclusion-to-accelerating-your-build-with-clang/ Hope this helps! On Tue, Mar 1, 2016 at 9:17 PM, ChrisBieneman via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > > On Mar 1, 2016, at 10:01 AM, Mehdi Amini

Hey Chris, Sedat was asking for a way to "to speedup my build" and those blog posts were really helpful to me. Anyway LLVM_DISTRIBUTION_COMPONENTS sounds very cool, hope you will push your code soon! On Tue, Mar 1, 2016 at 11:32 PM, Chris Bieneman <cbieneman at apple.com> wrote: > Fabio, the work I was mentioning here is an extension beyond those blog > posts. > >

> 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

On Fri, Mar 4, 2016 at 11:28 AM, Tilmann Scheller <tilmann at osg.samsung.com> wrote: > Hi Sedat, > > On 03/03/2016 08:09 AM, Sedat Dilek via llvm-dev wrote: >> >> It might be that a CLANG generated with LTO/PGO speeds up the build. >> Can you confirm this? > > Yes, a Clang host compiler built with LTO or PGO is generally faster than an > -O3 build. >

I had only a quick view 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 #

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