Just FYI, we discovered that GNU binutils 2.17 has a nasty bug in the linker that causes excessive link time when building llvm. We switched to using cvs binutils and our link times went from minutes to seconds. I didn't see anything about this on the web pages. It might be good information to add to the Getting Started guide. -Dave
> Just FYI, we discovered that GNU binutils 2.17 has a nasty bug in the > linker that causes excessive link time when building llvm. We switched > to using cvs binutils and our link times went from minutes to seconds.Is there a binutils snapshot that can be used instead ? Aaron
On Friday 15 June 2007 19:48, Aaron Gray wrote:> > Just FYI, we discovered that GNU binutils 2.17 has a nasty bug in the > > linker that causes excessive link time when building llvm. We switched > > to using cvs binutils and our link times went from minutes to seconds. > > Is there a binutils snapshot that can be used instead ?I would assume that any recent snapshot would have the fix. I don't know exactly when they went in. The "Linux binutils" apparently has the fix. I believe most Linux distributions supply that version. -Dave
On 6/16/07, David A. Greene <greened at obbligato.org> wrote:> Just FYI, we discovered that GNU binutils 2.17 has a nasty bug in the > linker that causes excessive link time when building llvm. We switched > to using cvs binutils and our link times went from minutes to seconds. > > I didn't see anything about this on the web pages. It might be good > information to add to the Getting Started guide.Here is the bug: http://sourceware.org/bugzilla/show_bug.cgi?id=3111 It was fixed in 2.17.50.0.4 Cheers, Rafael
On Saturday 16 June 2007 04:18, Rafael EspĂndola wrote:> On 6/16/07, David A. Greene <greened at obbligato.org> wrote: > > Just FYI, we discovered that GNU binutils 2.17 has a nasty bug in the > > linker that causes excessive link time when building llvm. We switched > > to using cvs binutils and our link times went from minutes to seconds. > > > > I didn't see anything about this on the web pages. It might be good > > information to add to the Getting Started guide. > > Here is the bug: > http://sourceware.org/bugzilla/show_bug.cgi?id=3111 > > It was fixed in 2.17.50.0.4Just to clarify, 2.17.50.0.4 is the "Linux binutils" which won't help those not working on Linux or not using the "Linux binutils." The "Linux binutils" is essentially a pre-release version of the next GNU binutils and as such it can sometimes include less than optimal patches. Again, FYI. -Dave
On Sat, 16 Jun 2007, [UTF-8] Rafael Esp?ndola wrote:> On 6/16/07, David A. Greene <greened at obbligato.org> wrote: >> Just FYI, we discovered that GNU binutils 2.17 has a nasty bug in the >> linker that causes excessive link time when building llvm. We switched >> to using cvs binutils and our link times went from minutes to seconds. >> >> I didn't see anything about this on the web pages. It might be good >> information to add to the Getting Started guide. > > Here is the bug: > http://sourceware.org/bugzilla/show_bug.cgi?id=3111 > > It was fixed in 2.17.50.0.4Excellent, thanks for the info. I added it to the end of: http://llvm.org/docs/GettingStarted.html#brokengcc -Chris -- http://nondot.org/sabre/ http://llvm.org/
Apparently Analagous Threads
- [LLVMdev] Improving link time building llvm
- [LLVMdev] Improving link time building llvm
- [LLVMdev] Parallel testsuite run breaks
- [LLVMdev] [RFC] Moving to Sphinx for LLVM and friends documentation (with partial implementation (in both 10pt and 12pt font)).
- [LLVMdev] Improving link time building llvm