[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug ld/11168] ld.exe CPU time >75 hours
From: |
jmihalicza at gmail dot com |
Subject: |
[Bug ld/11168] ld.exe CPU time >75 hours |
Date: |
15 Jan 2010 12:07:39 -0000 |
------- Additional Comments From jmihalicza at gmail dot com 2010-01-15 12:07
-------
(In reply to comment #3)
> Crazy C++ templated code take a crazy amount of time to compile/link on my
Yes, I agree, this is a separated example, but such things can appear even in
real applications when complex metaprograms are used.
> memory starved machine. This is hardly a ld bug.
Memory usage is 22 932 K, peak: 71 152 K.
My problem is the lack of scalability.
I get objects and assembly code with 'g++ -save-temps' for N = 7 and N = 8.
For N = 8 they are cca. 4 times bigger, I would expect ld to run 4 or even 10-20
times longer, but not forever.
For N = 7 it is ready in about a minute or less, actually didn't measure the ld
phase in itself.
For N = 8 it has been running for almost 96 hours now, which would mean a factor
of 5700 as a result of 4 times more symbols. I rather believe the process is
somehow stuck in an infinite loop.
(I know that there can be other factors and the process is not necessarily
linear, but the situation is still strange, see also the process properties
listed below.)
As a comparison I invoked 'nm -C' on the objects and got results in ~5.67s (N=7)
and ~189s (N=8), the factor was ~33.
I have two snapshots of some process properties:
CPU Time 24:20:22
CPU Usage full
Mem Usage 22 532 K
IO Read 6 458 677 777 B
IO Write 69 776 456 B
IO Other 1 981 332 B
CPU Time 95:59:41
CPU Usage full
Mem Usage 22 932 K Peak 71 152 K
IO Read 6 544 941 777 B
IO Write 149 104 922 B
IO Other 1 982 612 B
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
http://sourceware.org/bugzilla/show_bug.cgi?id=11168
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
- [Bug ld/11168] New: ld.exe CPU time >75 hours, jmihalicza at gmail dot com, 2010/01/14
- [Bug ld/11168] ld.exe CPU time >75 hours, jmihalicza at gmail dot com, 2010/01/14
- [Bug ld/11168] ld.exe CPU time >75 hours, hjl dot tools at gmail dot com, 2010/01/14
- [Bug ld/11168] ld.exe CPU time >75 hours, amodra at gmail dot com, 2010/01/14
- [Bug ld/11168] ld.exe CPU time >75 hours,
jmihalicza at gmail dot com <=
- [Bug ld/11168] ld.exe CPU time >75 hours, amodra at gmail dot com, 2010/01/15
- [Bug ld/11168] ld.exe CPU time >75 hours, jmihalicza at gmail dot com, 2010/01/15
- [Bug ld/11168] ld.exe CPU time >75 hours, amodra at gmail dot com, 2010/01/17
- [Bug ld/11168] ld.exe CPU time >75 hours, cvs-commit at gcc dot gnu dot org, 2010/01/18
- [Bug ld/11168] ld.exe CPU time >75 hours, amodra at gmail dot com, 2010/01/18
- [Bug ld/11168] ld.exe CPU time >75 hours, jmihalicza at gmail dot com, 2010/01/23