Launchpad has imported 14 comments from the remote bug at
http://sourceware.org/bugzilla/show_bug.cgi?id=3111.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2006-08-23T15:26:41+00:00 Doreille wrote:

This bug occurs with the binutils-060823 snapshot and  binutils-2.16.91.0.6-5
(fedora-5) on both x86-64 and i386 architectures. It do not occur with
binutils-2.15.94 (fedora-4).

When linking  C++ files compiled by GCC 4.1.1 with the -g option ld take 3
minutes to link . Without the -g option the link time was 5 seconds. The
obtained shared library has 17 MBytes size without debugging symbols and 59
MBytes size with debugging symbols.

Reply at: https://bugs.launchpad.net/binutils/+bug/69897/comments/0

------------------------------------------------------------------------
On 2006-08-23T15:35:04+00:00 Doreille wrote:

Created attachment 1243
gprof execution profile of ld

This is the gprof call graph profile data of  ld (binutils-060823 )  linking
the files with the dwarf2 symbols.

Reply at: https://bugs.launchpad.net/binutils/+bug/69897/comments/1

------------------------------------------------------------------------
On 2006-08-25T14:52:38+00:00 Hjl-tools wrote:

Please try the current Linux binutils at

http://www.kernel.org/pub/linux/devel/binutils/

and follow its release note closely.

Reply at: https://bugs.launchpad.net/binutils/+bug/69897/comments/2

------------------------------------------------------------------------
On 2006-08-25T16:40:29+00:00 Doreille wrote:

I have installed the latest binary rpm package
binutils-2.17.50.0.3-1.x86_64.rpm. With this version, the link time was
6m20.613s with the debugging symbols.
Without the debugging symbols, the link time was 4.369s.

Reply at: https://bugs.launchpad.net/binutils/+bug/69897/comments/3

------------------------------------------------------------------------
On 2006-08-25T16:44:12+00:00 Hjl-tools wrote:

Are you sure that you used the correct linker?

Reply at: https://bugs.launchpad.net/binutils/+bug/69897/comments/4

------------------------------------------------------------------------
On 2006-08-25T16:51:08+00:00 Hjl-tools wrote:

Is this the same bug as in commect #9 in PR 2342:

http://sources.redhat.com/bugzilla/show_bug.cgi?id=2342#c9

Reply at: https://bugs.launchpad.net/binutils/+bug/69897/comments/5

------------------------------------------------------------------------
On 2006-08-29T18:01:33+00:00 Doreille wrote:

I think this bug is the same as the one in comment #9 of PR 2342. With binutils
2.17.50.0.3 (linux patch applied) and the given test case slowld.tar.gz the link
time was 2m54.853s. After removing the debugging symbols with 'strip -g' the
link time become 6.386s.

I have another test case at
ftp://www.smr.ch/pub/smr/read/slow_ld_testcase.tar.bz2 with seven elf64 object
files where the link time was 1m7.316s with debugging symbols but 0.926s after a
'strip -g *.o'.


Reply at: https://bugs.launchpad.net/binutils/+bug/69897/comments/6

------------------------------------------------------------------------
On 2006-08-29T23:06:04+00:00 Hjl-tools wrote:

They are 2 different problems. With the previous patch, I got 18
sections:

time g++ -B/export/home/hjl/usr/bin/ -g -o ff3d trapFPE.o main.o FFThread.o
StaticCenter.o \
language/libfflanguage.a solver/libffsolve.a \
language/libpovlanguage.a geometry/libffgeometry.a \
algebra/libffalgebra.a utils/libffutils.a -pthread
FFThread.o: In function `FFThread::run()':
/space/rguenther/src/c++bench/ff3d/FFThread.cpp:79: undefined reference to
`__cxa_get_exception_ptr'
StaticCenter.o: In function `LagrangianFiniteElement':
./solver/LagrangianFiniteElement.hpp:365: undefined reference to
`__cxa_get_exception_ptr'
./solver/LagrangianFiniteElement.hpp:365: undefined reference to
`__cxa_get_exception_ptr'
./solver/LagrangianFiniteElement.hpp:365: undefined reference to
`__cxa_get_exception_ptr'
./solver/LagrangianFiniteElement.hpp:365: undefined reference to
`__cxa_get_exception_ptr'
StaticCenter.o:./solver/LagrangianFiniteElement.hpp:365: more undefined
references to `__cxa_get_exception_ptr' follow
collect2: ld returned 1 exit status
Command exited with non-zero status 1
18.32user 1.60system 0:19.92elapsed 100%CPU

The other problem is the N^2 issue mentioned in the previous bug report. It
is the same as this one. I posted a patch at

http://sourceware.org/ml/binutils/2006-08/msg00334.html

Reply at: https://bugs.launchpad.net/binutils/+bug/69897/comments/7

------------------------------------------------------------------------
On 2006-09-06T13:53:06+00:00 Rafael Ávila de Espíndola wrote:

I have done some testing on this problem:

link time just before 
http://sourceware.org/ml/binutils-cvs/2004-07/msg00124.html:
real    0m8.783s
user    0m8.049s
sys     0m0.628s

After:
real    13m49.449s
user    12m57.109s
sys     0m8.897s


current CVS:
real    3m52.577s
user    3m43.602s
sys     0m8.665s

current CVS + proposed patch:
real    0m5.780s
user    0m3.528s
sys     0m0.596s

Why the proposed patch wasn't committed? I am not familiar with binutils, but 
maybe I can help.

Reply at: https://bugs.launchpad.net/binutils/+bug/69897/comments/8

------------------------------------------------------------------------
On 2006-10-03T10:51:24+00:00 Rodsoft wrote:

ld´s changelog of 2.17.50.0.3 (or 4...) binutils says that this patch is
applied, but in fact it isn´t, as this version is still affected by this bug.
The patch can´t be seen in cvs either. IMO this is a major bug, the difference
between linking with and without -g is absurd... we can get from 6min to 30s
just by removing -g... Someone please commit the patch to cvs please.

Reply at: https://bugs.launchpad.net/binutils/+bug/69897/comments/9

------------------------------------------------------------------------
On 2006-10-03T12:50:25+00:00 Hjl-tools wrote:

Please follow the release note of the Linux binutils 2.17.50.0.5. You need
to apply patches in patches PROPERLY. Or you should use binary rpmes.

Reply at: https://bugs.launchpad.net/binutils/+bug/69897/comments/10

------------------------------------------------------------------------
On 2006-10-16T21:49:43+00:00 Hjl-tools wrote:

*** Bug 3321 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/binutils/+bug/69897/comments/11

------------------------------------------------------------------------
On 2006-10-30T23:44:00+00:00 Hjl-tools wrote:

http://sourceware.org/ml/binutils/2006-08/msg00334.html

is checked in. The maining one is

http://sourceware.org/ml/binutils/2006-04/msg00329.html

Reply at: https://bugs.launchpad.net/binutils/+bug/69897/comments/12

------------------------------------------------------------------------
On 2006-11-17T14:02:34+00:00 Alan Modra wrote:

Caching implemented in
http://sources.redhat.com/ml/binutils/2006-11/msg00190.html

Reply at: https://bugs.launchpad.net/binutils/+bug/69897/comments/14


** Changed in: binutils
   Importance: Unknown => Medium

** Bug watch added: Sourceware.org Bugzilla #2342
   http://sourceware.org/bugzilla/show_bug.cgi?id=2342

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/69897

Title:
  very slow ld

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to