search for: cmake_opts

On Fri, Dec 16, 2011 at 12:17:32PM -0500, David Fang wrote: >>> These results have far fewer failures than svn-trunk, and are also >>> comparable to bootstrapping with gcc-4.6.2, summarized here: >>> http://paste.lisp.org/display/126363 >>> (Unfortunately, I no longer have the whole build/test log for the gcc46 bootstrap.) >>> This consistency between

...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 n...

...gt;> >> 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 compilat...

>> These results have far fewer failures than svn-trunk, and are also >> comparable to bootstrapping with gcc-4.6.2, summarized here: >> http://paste.lisp.org/display/126363 >> (Unfortunately, I no longer have the whole build/test log for the gcc46 bootstrap.) >> This consistency between different bootstraps of the release gives me >> some hope that g++-4.0.1 is

...NOTE #1: CMake Version 2.8.8 is the minimum required(Ubuntu/precise ships v2.8.7 officially) # NOTE #2: For fast builds use recommended CMake >= v3.2 (used: v3.4.3) and Ninja (used: v1.6.0) # NOTE #3: How to check available cmake-options? # EXAMPLE #3: cd $BUILD_DIR ; cmake ../llvm -LA | egrep $CMAKE_OPTS # # CMake binary CMAKE="cmake" # CMake compiler options COMPILERS_CMAKE_OPTS="-DCMAKE_C_COMPILER=$COMPILER_CC -DCMAKE_CXX_COMPILER=$COMPILER_CXX" # NOTE-1: cmake/ninja: Use LLVM_PARALLEL_COMPILE_JOBS and LLVM_PARALLEL_LINK_JOBS options # NOTE-2: For fast builds use available (on...

...e" 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 >>>> >>&...

...m.org> wrote: > > 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. > > ***...

> On 7 May 2018, at 11:01, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Mon, May 7, 2018 at 5:52 AM, Brian Cain <brian.cain at gmail.com <mailto:brian.cain at gmail.com>> wrote: >> The simplest way to run a clang test case that I know of is to clone both >> llvm and clang repos, run all the tests, then run an individual test. >>

...can I force to use a different clang than "/home/sdi/src/llvm-toolchain/build/bin/clang"? I have no symlink to /usr/bin/clang. Thanks. Regards, - Sedat - P.S.: New build-script [build_clang-with-ninja.sh ] #!/bin/sh export LANG=C export LC_ALL=C cd build CMAKE="cmake" CMAKE_OPTS="-G Ninja -DCMAKE_C_COMPILER=clang-7 -DCMAKE_CXX_COMPILER=clang++-7 -DLLVM_PARALLEL_COMPILE_JOBS=2 -DLLVM_PARALLEL_LINK_JOBS=1 -DCMAKE_BUILD_TYPE=RELEASE -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_TARGETS_TO_BUILD=X86" $CMAKE ../llvm $CMAKE_OPTS ninja check-clang - EOF -

> > But on the Libc++AndAbiBuilder, there's no way to set the CMake > argument (or is there?): No, there isn't. Should be simple enough to add though. I'd add it as a dict param. On Mon, Oct 20, 2014 at 8:11 AM, Jonathan Roelofs <jonathan at codesourcery.com > wrote: > +Dan Albert > > On 10/20/14 4:53 AM, Renato Golin wrote: > > Folks, > > >

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 ma...

Hi, Jack! On Fri, Nov 2, 2012 at 6:18 PM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > Nick, > Have you noticed that llvm/clang svn produces the following linker > warnings on > 'make check-all'? > > Linking CXX executable Debug/AsanTest > ld: warning: direct access in > llvm::convertible_fwd_ostream::~convertible_fwd_ostream() to global weak >

On Mon, May 7, 2018 at 5:52 AM, Brian Cain <brian.cain at gmail.com> wrote: > The simplest way to run a clang test case that I know of is to clone both > llvm and clang repos, run all the tests, then run an individual test. > > IIRC like so: > > git clone llvm ...... > cd llvm/tools > git clone clang ..... > cd ../../ > mkdir build > cd build > cmake

Nick, Have you noticed that llvm/clang svn produces the following linker warnings on 'make check-all'? Linking CXX executable Debug/AsanTest ld: warning: direct access in llvm::convertible_fwd_ostream::~convertible_fwd_ostream() to global weak symbol vtable for llvm::convertible_fwd_ostream means the weak symbol cannot be overridden at runtime. This was likely caused by different

On Oct 25, 2011, at 6:09 AM, Marcello Maggioni wrote: > Hi, I'm trying to compile the latest clang/llvm SVN versions and I get > this error on multiple systems : Linking, not compiling, but still. I am getting a similar error when building this morning. > Undefined symbols for architecture x86_64: > "clang::Sema::checkPseudoObjectRValue(clang::Expr*)", referenced

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 #

Hi, I'm trying to compile the latest clang/llvm SVN versions and I get this error on multiple systems : (Compiling with gcc): llvm[4]: Compiling cc1_main.cpp for Debug+Asserts build llvm[4]: Compiling cc1as_main.cpp for Debug+Asserts build llvm[4]: Compiling driver.cpp for Debug+Asserts build llvm[4]: Linking Debug+Asserts executable clang

On Mon, Nov 11, 2013 at 11:03:47AM -0500, Jack Howarth wrote: > On Mon, Nov 11, 2013 at 06:46:47PM +0400, Alexander Potapenko wrote: > > This file is for configure+make build, not CMake, so I'm not sure why > > it's being included into your build (these failures aren't > > reproducible for me). > > Can you please list the exact steps you're doing to build

On Mon, Nov 11, 2013 at 06:46:47PM +0400, Alexander Potapenko wrote: > This file is for configure+make build, not CMake, so I'm not sure why > it's being included into your build (these failures aren't > reproducible for me). > Can you please list the exact steps you're doing to build LLVM with > CMake and make sure you don't have additional CFLAGS (LDFLAGS etc)

+Bob Wilson I don't know if this is a recent Apple regression, or if it's now catching something which had always been invalid. -bw On Mon, Nov 11, 2013 at 8:44 AM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > On Mon, Nov 11, 2013 at 11:03:47AM -0500, Jack Howarth wrote: > > On Mon, Nov 11, 2013 at 06:46:47PM +0400, Alexander Potapenko wrote: > > > This