search for: sginificant

...on my Linux quad core box. Whatever improvement can be achieved on this > seems pretty insignifant. Oh, it's significant. When I build the Cray compiler with only non-LLVM stuff changed, the actual compiles (the Cray stuff) finish before the LLVM figures out nothing has changed. This is a sginificant productivity loss. The Cray compiler uses a non-recursive make and so gets tons of parallelism the LLVM build simply can't see because it's recursive. > Furthermore, recursive make is necessary for automatic generation of > header dependencies, among other things. The makefiles gene...

...ox. Whatever improvement can be achieved on this >> seems pretty insignifant. > > Oh, it's significant. When I build the Cray compiler with only non-LLVM > stuff changed, the actual compiles (the Cray stuff) finish before the > LLVM figures out nothing has changed. This is a sginificant > productivity loss. How is that? Your compiler builds in less than 3 seconds? (IIRC, the numbers are more like 1.5 seconds with a warm cache on a Linux 4core 2.4 GHz machine) Maybe the LLVM build is starved because of your compiler's build. > The Cray compiler uses a non-recursive make...

...ment can be achieved on this >>> seems pretty insignifant. >> >> Oh, it's significant. When I build the Cray compiler with only non-LLVM >> stuff changed, the actual compiles (the Cray stuff) finish before the >> LLVM figures out nothing has changed. This is a sginificant >> productivity loss. > > How is that? Your compiler builds in less than 3 seconds? (IIRC, the I have never seen an LLVM up-to-date build take only three seconds. You must have a much faster machine than I do. >> The Cray compiler uses a non-recursive make and so >> gets...

greened at obbligato.org (David A. Greene) writes: >>> Oh, it's significant. When I build the Cray compiler with only non-LLVM >>> stuff changed, the actual compiles (the Cray stuff) finish before the >>> LLVM figures out nothing has changed. This is a sginificant >>> productivity loss. >> >> How is that? Your compiler builds in less than 3 seconds? (IIRC, the > > I have never seen an LLVM up-to-date build take only three seconds. You > must have a much faster machine than I do. $ ../llvm/configure && make -j4 ... $ t...

...ment can be achieved on this >>> seems pretty insignifant. >> >> Oh, it's significant.  When I build the Cray compiler with only non-LLVM >> stuff changed, the actual compiles (the Cray stuff) finish before the >> LLVM figures out nothing has changed.  This is a sginificant >> productivity loss. > > How is that? Your compiler builds in less than 3 seconds? (IIRC, the > numbers are more like 1.5 seconds with a warm cache on a Linux 4core 2.4 > GHz machine) Maybe the LLVM build is starved because of your compiler's > build. > >> The Cra...

Chris Lattner <clattner at apple.com> writes: >>> 1. It generates really slow build systems. >> >> In my Linux box, last time I checked (long time ago) the cmake build was >> a bit faster than the Makefiles. But this is a tricky terrain, because >> they are not identical, not on the features supported (and some have an >> impact on build-time) nor

On Oct 27, 2011, at 11:28 PM, Óscar Fuentes wrote: > Chris Lattner <clattner at apple.com> writes: > >> There are several major problems with CMake IMO: >> >> 1. It generates really slow build systems. > > In my Linux box, last time I checked (long time ago) the cmake build was > a bit faster than the Makefiles. But this is a tricky terrain, because >