Igor Pechtchanski wrote: > Please do. There is no obvious reason why this should be the correct > behavior.
I filed PR 22207 with the testcase. Oddly, the gcc-3.4 in Debian unstable does not emit the warnings: $ g++-3.4 spurious_uninitialized_testcase.ii -Wall -Werror -O2 -c $ g++-3.4 -v Reading specs from /usr/lib/gcc/i486-linux-gnu/3.4.5/specs Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --libexecdir=/usr/lib --with-gxx-include-dir=/usr/include/c++/3.4 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --program-suffix=-3.4 --enable-__cxa_atexit --enable-libstdcxx-allocator=mt --enable-clocale=gnu --enable-libstdcxx-debug --enable-java-gc=boehm --enable-java-awt=gtk --disable-werror i486-linux-gnu Thread model: posix gcc version 3.4.5 20050613 (prerelease) (Debian 3.4.4-1) ...which implies one of the following: - it's been fixed already on the 3.4.x tree - one of Debian's patches addresses it - it's cygwin/windows specific (though I can't see how that would be) Brian
