This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/32841] [4.3 regression] HUGE(1.0d0) is written a +Infinity on Darwin8
- From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 25 Jul 2007 05:28:12 -0000
- Subject: [Bug libfortran/32841] [4.3 regression] HUGE(1.0d0) is written a +Infinity on Darwin8
- References: <bug-32841-12313@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #13 from jvdelisle at gcc dot gnu dot org 2007-07-25 05:28 -------
This is interesting. Using valgrind induces a problem with huge(1.0_10) on
x86-64
[jerry@quasar test]$ ./a.out
3.4028235E+38 1.797693134862316E+308 1.1897314953572317650E+4932
[jerry@quasar test]$ valgrind ./a.out
==19036== Memcheck, a memory error detector.
==19036== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al.
==19036== Using LibVEX rev 1658, a library for dynamic binary translation.
==19036== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP.
==19036== Using valgrind-3.2.1, a dynamic binary instrumentation framework.
==19036== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et al.
==19036== For more details, rerun with: -v
==19036==
3.4028235E+38 1.797693134862316E+308 +Infinity
==19036==
==19036== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 5 from 1)
==19036== malloc/free: in use at exit: 0 bytes in 0 blocks.
==19036== malloc/free: 12 allocs, 12 frees, 25,910 bytes allocated.
==19036== For counts of detected errors, rerun with: -v
==19036== All heap blocks were freed -- no leaks are possible.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32841