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
Thus not 1.5GB but 750MB vs 450MB.
rguenther@murzim:/tmp> ~/bin/maxmem2.sh gcc-4.4 -S -o /dev/null -fPIE -Os test_node.i -std=gnu99 total: 743380 kB rguenther@murzim:/tmp> ~/bin/maxmem2.sh gcc-4.4 -S -o /dev/null -Os test_node.i -std=gnu99 total: 630756 kB
the -fPIE effect itself is even less recognizable.
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 murzim: /tmp> ~/bin/maxmem2.sh gcc-4.3 -S -o /dev/null -g -fstack-protector -fPIE -Os test_node.i -std=gnu99 murzim: /tmp> ~/bin/maxmem2.sh gcc-4.2 -S -o /dev/null -g -fstack-protector -fPIE -Os test_node.i -std=gnu99
total: 744108 kB
rguenther@
total: 719836 kB
rguenther@
total: 459757 kB
Thus not 1.5GB but 750MB vs 450MB.
rguenther@ murzim: /tmp> ~/bin/maxmem2.sh gcc-4.4 -S -o /dev/null -fPIE -Os test_node.i -std=gnu99 murzim: /tmp> ~/bin/maxmem2.sh gcc-4.4 -S -o /dev/null -Os test_node.i -std=gnu99
total: 743380 kB
rguenther@
total: 630756 kB
the -fPIE effect itself is even less recognizable.