[Bug libfortran/21376] libfortran "E" output format causes FPE
-- What|Removed |Added Target Milestone|--- |4.0.1 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21376
[Bug libfortran/21376] libfortran "E" output format causes FPE
--- Additional Comments From fxcoudert at gcc dot gnu dot org 2005-05-22 21:21 --- Fixed. Thanks for reporting! -- What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21376
[Bug libfortran/21376] libfortran "E" output format causes FPE
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-22 21:17 --- Subject: Bug 21376 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-05-22 21:17:43 Modified files: libgfortran: ChangeLog libgfortran/io : write.c Log message: PR libfortran/21376 * io/write.c (output_float): Rework logic to avoid call to log10 with argument equal to zero. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&r1=1.226&r2=1.227 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/write.c.diff?cvsroot=gcc&r1=1.37&r2=1.38 --- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-22 21:17 --- Subject: Bug 21376 CVSROOT:/cvs/gcc Module name:gcc Branch: gcc-4_0-branch Changes by: [EMAIL PROTECTED] 2005-05-22 21:17:44 Modified files: libgfortran: ChangeLog libgfortran/io : write.c Log message: PR libfortran/21376 * io/write.c (output_float): Rework logic to avoid call to log10 with argument equal to zero. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.163.2.37&r2=1.163.2.38 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/write.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.23.2.6&r2=1.23.2.7 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21376
[Bug libfortran/21376] libfortran "E" output format causes FPE
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-22 21:17 --- Subject: Bug 21376 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-05-22 21:17:43 Modified files: libgfortran: ChangeLog libgfortran/io : write.c Log message: PR libfortran/21376 * io/write.c (output_float): Rework logic to avoid call to log10 with argument equal to zero. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&r1=1.226&r2=1.227 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/write.c.diff?cvsroot=gcc&r1=1.37&r2=1.38 --- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-05-22 21:17 --- Subject: Bug 21376 CVSROOT:/cvs/gcc Module name:gcc Branch: gcc-4_0-branch Changes by: [EMAIL PROTECTED] 2005-05-22 21:17:44 Modified files: libgfortran: ChangeLog libgfortran/io : write.c Log message: PR libfortran/21376 * io/write.c (output_float): Rework logic to avoid call to log10 with argument equal to zero. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.163.2.37&r2=1.163.2.38 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/write.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.23.2.6&r2=1.23.2.7 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21376
[Bug libfortran/21376] libfortran "E" output format causes FPE
--- Additional Comments From fxcoudert at gcc dot gnu dot org 2005-05-22 18:35 --- Patch submitted for review. -- What|Removed |Added URL||http://gcc.gnu.org/ml/fortra ||n/2005-05/msg00249.html Keywords||patch http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21376
[Bug libfortran/21376] libfortran "E" output format causes FPE
-- What|Removed |Added AssignedTo|unassigned at gcc dot gnu |fxcoudert at gcc dot gnu dot |dot org |org Status|UNCONFIRMED |ASSIGNED Ever Confirmed||1 GCC build triplet|i686-pc-linux-gnu | GCC host triplet|i686-pc-linux-gnu | GCC target triplet|i686-pc-linux-gnu | Last reconfirmed|-00-00 00:00:00 |2005-05-09 11:29:26 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21376
[Bug libfortran/21376] libfortran "E" output format causes FPE
--- Additional Comments From prw at ceiriog1 dot demon dot co dot uk
2005-05-04 17:28 ---
The problem occurred in a large finite element analysis code I developed.
The toplevel logic was written in C++, and this was linked to a venerable
public domain numerical analysis library in Fortran. My testcase consists
of the following two files. You only get a floating point exception
if IEEE floating point exceptions are enabled. I don't know if it is possible
to do this from a pure Fortran program, but it is certainly possible to
do from C, and I find it important to do this in numerical codes so that
I can see errors where they occur rather than just propagating NaN's through
the program.
File "toplevel.c":
#include
main()
{
feenableexcept(FE_DIVBYZERO | FE_INVALID | FE_OVERFLOW );
killer_();
}
File "killer.f":
subroutine killer
write(6,'(x,e10.4)') 1.0
end
gcc -c toplevel.c
gfortran -c killer.f
gcc toplevel.o killer.o -lgfortran
./a.out
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21376
[Bug libfortran/21376] libfortran "E" output format causes FPE
--- Additional Comments From fxcoudert at gcc dot gnu dot org 2005-05-04 16:41 --- I'm interested: you do have a testcase that produces this failure on i686-pc-linux-gnu? If so, I will make a testcase out of it and propose your patch for review... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21376
