gcc

Comment 38 for bug 398403

Revision history for this message
In , Rguenth (rguenth) wrote :

(In reply to comment #4)
> This is likely caused by the DF merge. There are numerous bugs about this
> already and nothing really can be done here.
>
> Btw, my numbers are
>
> rguenther@murzim:/tmp> ~/bin/maxmem2.sh gcc-4.4 -S -o /dev/null -g
> -fstack-protector -fPIE -Os test_node.i -std=gnu99
> total: 744108 kB
> rguenther@murzim:/tmp> ~/bin/maxmem2.sh gcc-4.3 -S -o /dev/null -g
> -fstack-protector -fPIE -Os test_node.i -std=gnu99
> total: 719836 kB
> rguenther@murzim:/tmp> ~/bin/maxmem2.sh gcc-4.2 -S -o /dev/null -g
> -fstack-protector -fPIE -Os test_node.i -std=gnu99
> total: 459757 kB

> ~/bin/maxmem2.sh gcc-4.6 -S -o /dev/null t.i -v -std=gnu99 -Os -fPIE -fstack-protector -g
total: 772239 kB
> ~/bin/maxmem2.sh gcc-4.7 -S -o /dev/null t.i -v -std=gnu99 -Os -fPIE -fstack-protector -g --param ggc-min-expand=100 --param ggc-min-heapsize=131072
total: 794883 kB

we're continuing to increase, thus re-confirmed.