search for: cmake_options

...ldbot, but not for darwin8.) Knowing what I've learned so far, the > effort would be similar, perhaps even duplicate to just trying to fix > things directly with g++-4.0.1. Time will tell, I suppose. > > Fang > David, I suspect you might be running into problem with... CMAKE_OPTIONS="-DLLVM_BUILD_32_BITS:BOOL=ON -DLLVM_TARGETS_TO_BUILD=PowerPC" not working properly in the llvm 2.9 release for building with cmake. http://llvm.org/bugs/show_bug.cgi?id=9957 If you can tolerate the complete build by changing this to... CMAKE_OPTIONS="-DLLVM_BUILD_32_BITS:BOOL=ON...

On linux (not Windows) I doubt using Ninja vs make will make drastic differences.. (Others with actual numbers please chime in to correct me) /* I think the difference could be more beneficial if you're doing incremental builds, but I don't think that is what you're doing.. */ On Thu, Feb 25, 2016 at 1:51 PM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On

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

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

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

On Thu, Feb 25, 2016 at 7:55 AM, C Bergström <cbergstrom at pathscale.com> wrote: > On linux (not Windows) I doubt using Ninja vs make will make drastic > differences.. (Others with actual numbers please chime in to correct > me) > > /* > I think the difference could be more beneficial if you're doing > incremental builds, but I don't think that is what

> 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 use... > > CMAKE_JOBS="1" > ##CMAKE_JOBS=$(($(getconf _NPROCESSORS_ONLN)+1)) >

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

On Mon, May 7, 2018 at 4:03 PM, Amara Emerson <aemerson at apple.com> wrote: > 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> 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

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

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

...issue... > > cd llvm-3.4 > mv ../clang-3.4 tools/clang > mv ../compiler-rt-3.4 projects/compiler-rt > mv ../test-suite-3.4 projects/test-suite > mkdir build > pushd build > /sw/src/fink.build/llvm34-3.4-0/llvm-3.4/build /sw/src/fink.build/llvm34-3.4-0/llvm-3.4 > cmake $CMAKE_OPTIONS -DCMAKE_INSTALL_PREFIX=/sw/opt/llvm-3.4 -DLLVM_ENABLE_ASSERTIONS=OFF -DCMAKE_BUILD_TYPE=Release .. > -- The C compiler identification is Clang 5.0.0 > -- The CXX compiler identification is Clang 5.0.0 > -- Check for working C compiler: /sw/var/lib/fink/path-prefix-clang/cc > -- Check fo...

...uilding llvm svn as follows for years without issue... cd llvm-3.4 mv ../clang-3.4 tools/clang mv ../compiler-rt-3.4 projects/compiler-rt mv ../test-suite-3.4 projects/test-suite mkdir build pushd build /sw/src/fink.build/llvm34-3.4-0/llvm-3.4/build /sw/src/fink.build/llvm34-3.4-0/llvm-3.4 cmake $CMAKE_OPTIONS -DCMAKE_INSTALL_PREFIX=/sw/opt/llvm-3.4 -DLLVM_ENABLE_ASSERTIONS=OFF -DCMAKE_BUILD_TYPE=Release .. -- The C compiler identification is Clang 5.0.0 -- The CXX compiler identification is Clang 5.0.0 -- Check for working C compiler: /sw/var/lib/fink/path-prefix-clang/cc -- Check for working C compiler...

...../clang-3.4 tools/clang > > mv ../compiler-rt-3.4 projects/compiler-rt > > mv ../test-suite-3.4 projects/test-suite > > mkdir build > > pushd build > > /sw/src/fink.build/llvm34-3.4-0/llvm-3.4/build > /sw/src/fink.build/llvm34-3.4-0/llvm-3.4 > > cmake $CMAKE_OPTIONS -DCMAKE_INSTALL_PREFIX=/sw/opt/llvm-3.4 > -DLLVM_ENABLE_ASSERTIONS=OFF -DCMAKE_BUILD_TYPE=Release .. > > -- The C compiler identification is Clang 5.0.0 > > -- The CXX compiler identification is Clang 5.0.0 > > -- Check for working C compiler: /sw/var/lib/fink/path-prefix-clang...