Try harder to trigger an exception. On architectures where floating-point

exceptions are deferred, we might not see the exception before another
floating-point instruction is executed.  This is especially true on the i387
where we don't see underflow/overflow until the result is stored into memory.

1 files changed, 7 insertions, 1 deletions

diff --git a/src/regress/lib/libc/ieeefp/except/except.c b/src/regress/lib/libc/ieeefp/except/except.c
index 22bd6809a8..1d11877777 100644
--- a/src/regress/lib/libc/ieeefp/except/except.c
+++ b/src/regress/lib/libc/ieeefp/except/except.c
@@ -1,4 +1,4 @@
-/*      $OpenBSD: except.c,v 1.9 2004/12/22 00:54:39 david Exp $        */
+/*      $OpenBSD: except.c,v 1.10 2006/05/15 14:00:22 kettenis Exp $    */
 
 #include <sys/types.h>
 #include <unistd.h>
@@ -97,5 +97,11 @@ main(int argc, char *argv[])
                 errx(1, "unrecognized condition %s", argv[1]);
         }
 
+        /*
+         * attempt to trigger the exception on machines where
+         * floating-point exceptions are deferred.
+         */
+        x = one * one;
+
         errx(1, "signal wasn't caught");
 }