[Bug fortran/46703] Wrong I/O output (only) when running under valgrind
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46703 Jerry DeLisle jvdelisle at gcc dot gnu.org changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|--- |INVALID --- Comment #7 from Jerry DeLisle jvdelisle at gcc dot gnu.org --- Closing as invalid.
[Bug fortran/46703] Wrong I/O output (only) when running under valgrind
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46703 Bud Davis bdavis at gcc dot gnu.org changed: What|Removed |Added CC||bdavis at gcc dot gnu.org --- Comment #5 from Bud Davis bdavis at gcc dot gnu.org --- From the world of 2013gcc-4.8 / FC18 / i386 The example posted above gives good answers when compiled and ran. And all zeroes when ran under valgrind.
[Bug fortran/46703] Wrong I/O output (only) when running under valgrind
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46703 --- Comment #6 from Bud Davis bdavis at gcc dot gnu.org --- It is a problem with Valgrind. One that is even mentioned in the (valgrind) manual. https://bugs.kde.org/show_bug.cgi?id=197915 It has been open for about 4 years, not fixed yet. Short summary. Don't use valgrind on real's larger than 64 bits. --bud davis
[Bug fortran/46703] Wrong I/O output (only) when running under valgrind
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46703 --- Comment #4 from Daniel Franke dfranke at gcc dot gnu.org 2011-07-24 18:53:21 UTC --- Any news here? May this report be closed?
[Bug fortran/46703] Wrong I/O output (only) when running under valgrind
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46703 Daniel Franke dfranke at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed||2010.12.27 00:23:27 CC||dfranke at gcc dot gnu.org Ever Confirmed|0 |1 --- Comment #2 from Daniel Franke dfranke at gcc dot gnu.org 2010-12-27 00:23:27 UTC --- (In reply to comment #1) Maybe yet another of x86's extra floating point precision effects. I suppose where valgrind needs to do its verifications, it interrupts the program and saves/restores the registers (to memory), thus losing the extra precision. Seconded. Simple test: does -ffloat-store change the output as well?
[Bug fortran/46703] Wrong I/O output (only) when running under valgrind
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46703 --- Comment #3 from Jerry DeLisle jvdelisle at gcc dot gnu.org 2010-12-27 01:03:55 UTC --- -ffloat-store is the first thing I tried and no change. However, the run-time side, libgfortran, is not compiled normally with -ffloat-store so maybe we should try that.
[Bug fortran/46703] Wrong I/O output (only) when running under valgrind
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46703 Mikael Morin mikael at gcc dot gnu.org changed: What|Removed |Added CC||mikael at gcc dot gnu.org --- Comment #1 from Mikael Morin mikael at gcc dot gnu.org 2010-11-29 19:26:37 UTC --- Maybe yet another of x86's extra floating point precision effects. I suppose where valgrind needs to do its verifications, it interrupts the program and saves/restores the registers (to memory), thus losing the extra precision. Try to ask to the valgrind developers, the problems looks very valgrind-related.
