Thanks for submitting this bug for gcc-4.4; a similar one (#631627) exists for gcc-4.6. My analysis of this bug (with workaround) is here: http://lists.debian.org/debian-gcc/2011/06/msg00209.html -- Ludovic Brenta.