------- Comment #4 from kargl at gcc dot gnu dot org 2009-06-21 17:12 -------
(In reply to comment #3)
> I see no memory issues or memory growth on x85-64-linux-gnu with -m64 or
> -m32.
> This appears to be target specific. Checked with 4.4.1 and latest trunk.
>
I think there is a leak. After 3 iterations, I have
REMOVE:kargl[67] ./z
1 1234567890123456789012345678901234567890123456789012
2 1234567890123456789012345678901234567890123456789012
3 1234567890123456789012345678901234567890123456789012
last pid: 17063; load averages: 0.93, 0.52, 0.34 up 0+17:51:38 10:09:24
44 processes: 2 running, 42 sleeping
CPU: 45.1% user, 0.0% nice, 5.6% system, 0.0% interrupt, 49.3% idle
Mem: 299M Active, 438M Inact, 198M Wired, 39M Cache, 110M Buf, 11M Free
Swap: 1024M Total, 60M Used, 964M Free, 5% Inuse
PID USERNAME THR PRI NICE SIZE RES STATE C TIME CPU COMMAND
17063 kargl 1 119 0 247M 246M CPU1 0 2:30 100.34% z
With each iteration, the SIZE grows by about 80M.
Anyone have valgrind? Last I checked, algrind did not run on FreeBSD.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40508
