Update.

1998-02-11  Andreas Jaeger  <aj@arthur.rhein-neckar.de>

	* manual/memory.texi (Using the Memory Debugger): Fix typo.

	* math/libm-test.c (modf_test): Add one more test for modf.

3 files changed, 12 insertions, 1 deletions

diff --git a/ChangeLog b/ChangeLog
index d254d7a419..f8dc304692 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+1998-02-11  Andreas Jaeger  <aj@arthur.rhein-neckar.de>
+
+	* manual/memory.texi (Using the Memory Debugger): Fix typo.
+
+	* math/libm-test.c (modf_test): Add one more test for modf.
+
 1998-02-11 14:39  Ulrich Drepper  <drepper@happy.cygnus.com>
 
 	* sysdeps/unix/sysv/linux/i386/sigaction.c (__libc_missing_rt_sigs):
diff --git a/manual/memory.texi b/manual/memory.texi
index 421ec797f7..4e42b47add 100644
--- a/manual/memory.texi
+++ b/manual/memory.texi
@@ -898,7 +898,7 @@ behaviour of the program it is no wise idea to call @code{mtrace} in all
 programs.  Just imagine you debug a program using @code{mtrace} and all
 other programs used in the debug sessions also trace their @code{malloc}
 calls.  The output file would be the same for all programs and so is
-unusable.  Therefore on should call @code{mtrace} only if compiled for
+unusable.  Therefore one should call @code{mtrace} only if compiled for
 debugging.  A program could therefore start like this:
 
 @example
diff --git a/math/libm-test.c b/math/libm-test.c
index 13f7cf315b..f35ef41423 100644
--- a/math/libm-test.c
+++ b/math/libm-test.c
@@ -1714,6 +1714,11 @@ modf_test (void)
   result = FUNC(modf) (21, &intpart);
   check ("modf (21, &x) returns 0", result, 0);
   check ("modf (21, &x) sets x to 21", intpart, 21);
+
+  result = FUNC(modf) (89.6, &intpart);
+  check_eps ("modf (89.6, &x) returns 0.6", result, 0.6,
+	     CHOOSE(6e-15L, 6e-15, 2e-6));
+  check ("modf (89.6, &x) sets x to 89", intpart, 89);
 }