search for: wearefam

...e maximum number of concurrent compilation jobs. LLVM_PARALLEL_COMPILE_JOBS:STRING=3 //Define the maximum number of concurrent link jobs. LLVM_PARALLEL_LINK_JOBS:STRING=1 CMAKE_GENERATOR:INTERNAL=Ninja $ LC_ALL=C ls -alt logs/3.8.0rc3_clang-3-8-0-rc3_cmake-3-4-3_ninja-1-6-0/ total 360 drwxr-xr-x 2 wearefam wearefam 4096 Feb 25 19:58 . drwxr-xr-x 6 wearefam wearefam 4096 Feb 25 19:58 .. -rw-r--r-- 1 wearefam wearefam 130196 Feb 25 19:54 install-log_llvm-toolchain-3.8.0rc3.txt -rw-r--r-- 1 wearefam wearefam 205762 Feb 25 19:51 build-log_llvm-toolchain-3.8.0rc3.txt -rw-r--r-- 1 wearefam wearefam 14...

...COMPILE_JOBS:STRING=3 >> //Define the maximum number of concurrent link jobs. >> LLVM_PARALLEL_LINK_JOBS:STRING=1 >> CMAKE_GENERATOR:INTERNAL=Ninja >> >> $ LC_ALL=C ls -alt logs/3.8.0rc3_clang-3-8-0-rc3_cmake-3-4-3_ninja-1-6-0/ >> total 360 >> drwxr-xr-x 2 wearefam wearefam 4096 Feb 25 19:58 . >> drwxr-xr-x 6 wearefam wearefam 4096 Feb 25 19:58 .. >> -rw-r--r-- 1 wearefam wearefam 130196 Feb 25 19:54 >> install-log_llvm-toolchain-3.8.0rc3.txt >> -rw-r--r-- 1 wearefam wearefam 205762 Feb 25 19:51 >> build-log_llvm-toolchain-3....

...of concurrent link jobs. > >>> LLVM_PARALLEL_LINK_JOBS:STRING=1 > >>> CMAKE_GENERATOR:INTERNAL=Ninja > >>> > >>> $ LC_ALL=C ls -alt > logs/3.8.0rc3_clang-3-8-0-rc3_cmake-3-4-3_ninja-1-6-0/ > >>> total 360 > >>> drwxr-xr-x 2 wearefam wearefam 4096 Feb 25 19:58 . > >>> drwxr-xr-x 6 wearefam wearefam 4096 Feb 25 19:58 .. > >>> -rw-r--r-- 1 wearefam wearefam 130196 Feb 25 19:54 > >>> install-log_llvm-toolchain-3.8.0rc3.txt > >>> -rw-r--r-- 1 wearefam wearefam 205762 Feb 25 19:51...

...pprox. 1h from 2 to 3 hours when using CMAKE instead of CONFIGURE/MAKE (logs deleted for LLVM v3.8.0rc2). Building always done with one single parallel-compile-jobs. When using CMAKE $COMPILER does not matter, it's approx. 3 hours build-time. $ cat statistics/3.8.0rc3*/build*.txt -rw-r--r-- 1 wearefam wearefam 138872 Feb 25 10:25 logs/3.8.0rc3_clang-compiled/install-log_llvm-toolchain-3.8.0rc3.txt -rw-r--r-- 1 wearefam wearefam 216544 Feb 25 10:22 logs/3.8.0rc3_clang-compiled/build-log_llvm-toolchain-3.8.0rc3.txt -rw-r--r-- 1 wearefam wearefam 14476 Feb 25 07:29 logs/3.8.0rc3_clang-compiled/con...

...t;> >>> LLVM_PARALLEL_LINK_JOBS:STRING=1 >> >>> CMAKE_GENERATOR:INTERNAL=Ninja >> >>> >> >>> $ LC_ALL=C ls -alt >> logs/3.8.0rc3_clang-3-8-0-rc3_cmake-3-4-3_ninja-1-6-0/ >> >>> total 360 >> >>> drwxr-xr-x 2 wearefam wearefam 4096 Feb 25 19:58 . >> >>> drwxr-xr-x 6 wearefam wearefam 4096 Feb 25 19:58 .. >> >>> -rw-r--r-- 1 wearefam wearefam 130196 Feb 25 19:54 >> >>> install-log_llvm-toolchain-3.8.0rc3.txt >> >>> -rw-r--r-- 1 wearefam wearefam 2057...

...STRING=1 >>>>>>> CMAKE_GENERATOR:INTERNAL=Ninja >>>>>>> >>>>>>> $ LC_ALL=C ls -alt >>>> logs/3.8.0rc3_clang-3-8-0-rc3_cmake-3-4-3_ninja-1-6-0/ >>>>>>> total 360 >>>>>>> drwxr-xr-x 2 wearefam wearefam 4096 Feb 25 19:58 . >>>>>>> drwxr-xr-x 6 wearefam wearefam 4096 Feb 25 19:58 .. >>>>>>> -rw-r--r-- 1 wearefam wearefam 130196 Feb 25 19:54 >>>>>>> install-log_llvm-toolchain-3.8.0rc3.txt >>>>>>> -rw-r--...

...isc-usage_llvm-toolchain-3.8.0rc3_clang-3-8-0-rc3_cmake-3-4-3_ninja-1-6-0_compile-jobs-2_link-jobs-1.txt 315 llvm 941 llvm-build 609 /opt/llvm-toolchain-3.8.0rc3 $ cat build-time_llvm-toolchain-3.8.0rc3_clang-3-8-0-rc3_cmake-3-4-3_ninja-1-6-0_compile-jobs-2_link-jobs-1.txt -rw-r--r-- 1 wearefam wearefam 130196 Feb 25 22:26 logs/3.8.0rc3_clang-3-8-0-rc3_cmake-3-4-3_ninja-1-6-0_compile-jobs-2_link-jobs-1/install-log_llvm-toolchain-3.8.0rc3.txt -rw-r--r-- 1 wearefam wearefam 205762 Feb 25 22:18 logs/3.8.0rc3_clang-3-8-0-rc3_cmake-3-4-3_ninja-1-6-0_compile-jobs-2_link-jobs-1/build-log_llvm-to...

On Thu, Feb 25, 2016 at 7:37 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> On Feb 24, 2016, at 9:55 PM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Hi, >> >> I switched from "configure and make" to "cmake" build-system and >> wanted to speedup my build. >> >> In my build-script I

...s ] Hi, I already reported this when playing 1st time with my llvm-toolchain v3.6.0rc2 and mesa v10.3.7 [1]. The issue still remains in mesa v10.4.4. So, this is a field test to see if LLVM/Clang v3.6.0rc2 fits my needs. I see the following build-error... ... make[4]: Entering directory `/home/wearefam/src/mesa/mesa-git/src/mapi' CC shared_glapi_libglapi_la-entry.lo clang version 3.6.0 (tags/RELEASE_360/rc2) Target: x86_64-unknown-linux-gnu Thread model: posix Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-...

...>> v3.6.0rc2 and mesa v10.3.7 [1]. >> The issue still remains in mesa v10.4.4. >> >> So, this is a field test to see if LLVM/Clang v3.6.0rc2 fits my needs. >> >> I see the following build-error... >> ... >> >> make[4]: Entering directory `/home/wearefam/src/mesa/mesa-git/src/mapi' >> CC shared_glapi_libglapi_la-entry.lo >> clang version 3.6.0 (tags/RELEASE_360/rc2) >> Target: x86_64-unknown-linux-gnu >> Thread model: posix >> Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6 >> Found...

...CMake Error at cmake/modules/CheckAtomic.cmake:36 (message): Host compiler appears to require libatomic, but cannot find it. Call Stack (most recent call first): cmake/config-ix.cmake:296 (include) CMakeLists.txt:407 (include) -- Configuring incomplete, errors occurred! See also "/home/wearefam/src/llvm-toolchain/llvm-build/CMakeFiles/CMakeOutput.log". See also "/home/wearefam/src/llvm-toolchain/llvm-build/CMakeFiles/CMakeError.log". I would like to see something telling me my host-compiler is not supported and I need a minimum version ( My host-system is Ubuntu/precise AM...

...>> v3.6.0rc2 and mesa v10.3.7 [1]. >> The issue still remains in mesa v10.4.4. >> >> So, this is a field test to see if LLVM/Clang v3.6.0rc2 fits my needs. >> >> I see the following build-error... >> ... >> >> make[4]: Entering directory `/home/wearefam/src/mesa/mesa-git/src/mapi' >> CC shared_glapi_libglapi_la-entry.lo >> clang version 3.6.0 (tags/RELEASE_360/rc2) >> Target: x86_64-unknown-linux-gnu >> Thread model: posix >> Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6 >> Found...

...MAKE_GENERATOR:INTERNAL=Ninja >>>>>>>>> >>>>>>>>> $ LC_ALL=C ls -alt >>>>>> logs/3.8.0rc3_clang-3-8-0-rc3_cmake-3-4-3_ninja-1-6-0/ >>>>>>>>> total 360 >>>>>>>>> drwxr-xr-x 2 wearefam wearefam 4096 Feb 25 19:58 . >>>>>>>>> drwxr-xr-x 6 wearefam wearefam 4096 Feb 25 19:58 .. >>>>>>>>> -rw-r--r-- 1 wearefam wearefam 130196 Feb 25 19:54 >>>>>>>>> install-log_llvm-toolchain-3.8.0rc3.txt >>>...

[ Original posting see [1] ] >From [1]: ... Added: llvm/tags/RELEASE_380/rc3/ (props changed) - copied from r261685, llvm/branches/release_38/ ... The LLVM Git repositories have no "rc3" tag in "release_38" branch (as an example llvm.git#release_38 see [2]). Who is responsible for that or maybe better... can you activate the responsible(s)? Helpful is to add

...t a typo, nevertheless LLVM_ENABLE_LTO does not work! > > [ ... ] > -- Configuring done > -- Generating done > CMake Warning: > Manually-specified variables were not used by the project: > > LLVM_ENABLE_LTO > > > -- Build files have been written to: > /home/wearefam/src/llvm-toolchain/llvm-build > > Do you need more input? > > Thanks! > I found in "http://llvmweekly.org/issue/110" [ llvm.src/cmake/modules/HandleLLVMOptions.cmake ] option(LLVM_ENABLE_LTO "Enable link-time optimization" OFF) append_if(LLVM_ENABLE_LTO "-...

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

On 11 Feb 2015, at 11:16, Sedat Dilek <sedat.dilek at gmail.com> wrote: > > On Wed, Feb 11, 2015 at 12:09 AM, Emil Velikov <emil.l.velikov at gmail.com> wrote: >> On 10/02/15 13:17, Dimitry Andric wrote: >>> On 09 Feb 2015, at 18:52, Sedat Dilek <sedat.dilek at gmail.com> wrote: >>>> >>>> On Mon, Feb 9, 2015 at 6:44 PM, Emil Velikov

..._ATOMICS -- Performing Test COMPILER_RT_TARGET_HAS_ATOMICS - Success -- Clang version: 3.8.0 -- Performing Test CXX_SUPPORTS_NO_NESTED_ANON_TYPES_FLAG -- Performing Test CXX_SUPPORTS_NO_NESTED_ANON_TYPES_FLAG - Failed -- Configuring done -- Generating done -- Build files have been written to: /home/wearefam/src/llvm-toolchain/llvm-build -------------- next part -------------- A non-text attachment was scrubbed... Name: build_llvm-toolchain.sh Type: application/x-sh Size: 3786 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160225/0393e162/attachment.sh>