I can't reproduce this bug anymore with GCC 4.7 (but still with GCC 4.6). So it seems this was a GCC bug which is now fixed.
I can't reproduce this bug anymore with GCC 4.7 (but still with GCC 4.6). So it seems this was a GCC bug which is now fixed.