------- Comment #14 from dfranke at gcc dot gnu dot org 2008-06-18 16:48 ------- > Question: I get the following: > /tmp/ccpoBhQR.f90:8: warning: 'junk_2' is used uninitialized in this > function > What puzzles me is that one gets a /tmp/... filename and not the filename one > passed to "gfortran -cpp". Is this expected? I thought that when using libcpp > directly, no temporary file is written anymore.
Heisenbug it seems. On x86_64 (20080617) I get: $> gfortran-svn -Wall -O pr36342.F90 pr36342.F90: In function 'test': pr36342.F90:4: warning: 'junk_2' is used uninitialized in this function Running f951 as output by "gfortran [...] -v" gives: pr36342.F90: In function 'test': pr36342.F90:4: warning: 'junk_2' is used uninitialized in this function BUT, prefixing valgrind (otherwise identical to the call above) results in: /tmp/ccIl84Yu.f90: In function 'test': /tmp/ccIl84Yu.f90:4: warning: 'junk_2' is used uninitialized in this function In addition, valgrind shows multiple invalid-reads as quoted in earlier comments. $> gfortran-svn -v Using built-in specs. Target: x86_64-unknown-linux-gnu Configured with: /data/home/daniel/svn/gcc-svn/configure --prefix=/data/home/daniel/x86_64-unknown-linux-gnu/gcc --program-suffix=-svn --with-gmp=/data/home/daniel/x86_64-unknown-linux-gnu/gmp-4.2.1 --with-mpfr=/data/home/daniel/x86_64-unknown-linux-gnu/mpfr-2.2.1 --with-system-zlib --enable-bootstrap --enable-threads=posix --enable-shared --enable-version-specific-runtime-libs --enable-languages=c,fortran --disable-nls --disable-multilib --disable-libmudflap Thread model: posix gcc version 4.4.0 20080617 (experimental) (GCC) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36342
