The upstream bug report regarding this issue is PR11716, it appears they didn't feel like fixing it for gcc 3.3 but have fixed it for gcc 3.4. Chris http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11716