This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/46703] Wrong I/O output (only) when running under valgrind
- From: "dfranke at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 27 Dec 2010 00:23:41 +0000
- Subject: [Bug fortran/46703] Wrong I/O output (only) when running under valgrind
- Auto-submitted: auto-generated
- References: <bug-46703-4@http.gcc.gnu.org/bugzilla/>
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?