1999-08-26 Craig Burley <craig@jcb-sc.com>
+ * gcc.c-torture/execute/990826-0.c: New test.
+ * g77.c-torture/execute/19990826-0.f: New test.
+
* g77.f-torture/noncompile/970626-2.f: New test.
1999-08-25 Paul Burchard <burchard@pobox.com>
--- /dev/null
+* From: niles@fan745.gsfc.nasa.gov
+* To: fortran@gnu.org
+* Cc: niles@fan745.gsfc.nasa.gov
+* Subject: problem with DNINT() on Linux/Alpha.
+* Date: Sun, 06 Jun 1999 16:39:35 -0400
+* X-UIDL: 6aa9208d7bda8b6182a095dfd37016b7
+
+ IF (DNINT(0.0D0) .NE. 0.) CALL ABORT
+ STOP
+ END
+
+* Result on Linux/i386: " 0." (and every other computer!)
+* Result on Linux/alpha: " 3.6028797E+16"
+
+* It seems to work fine if I change it to the generic NINT(). Probably
+* a name pollution problem in the new C library, but it seems bad. no?
+
+* Thanks,
+* Rick Niles.
--- /dev/null
+/*
+From: niles@fan745.gsfc.nasa.gov
+To: fortran@gnu.org
+Subject: Re: Scary problems in g77 for RedHat 6.0. (glibc-2.1)
+Date: Sun, 06 Jun 1999 23:37:23 -0400
+X-UIDL: 9c1e40c572e3b306464f703461764cd5
+*/
+
+#include <stdio.h>
+#include <math.h>
+
+int
+main()
+{
+ if (floor (0.1) != 0.)
+ abort ();
+ return 0;
+}
+
+/*
+It will result in 36028797018963968.000000 on Alpha RedHat Linux 6.0
+using glibc-2.1 at least on my 21064. This may result in g77 bug
+reports concerning the INT() function, just so you know.
+
+ Thanks,
+ Rick Niles.
+*/