From b6df7dd7082e3c8d4bd88a708036abc53292e90e Mon Sep 17 00:00:00 2001
From: Nick Patrick <npatrick04@gmail.com>
Date: Sat, 20 Jul 2013 21:16:41 -0500
Subject: [PATCH] There doesn't appear to be any need for inhibiting floating
 point underflow in ansification for CLISP as of 2.49.

[1]> least-positive-single-float
1.1754944E-38
[2]> (coerce * 'single-float)
1.1754944E-38
---
 src/cold/ansify.lisp | 28 ----------------------------
 1 file changed, 28 deletions(-)

diff --git a/src/cold/ansify.lisp b/src/cold/ansify.lisp
index 901286d..0e62ea6 100644
--- a/src/cold/ansify.lisp
+++ b/src/cold/ansify.lisp
@@ -10,34 +10,6 @@
 ;;;; provided with absolutely no warranty. See the COPYING and CREDITS
 ;;;; files for more information.
 
-;;;; CLISP issues
-
-;;; as explained on #lisp ca. October 2003:
-;;;   <Krystof> chandler: nope, I'm blaming another clisp bug
-;;;   <Krystof> [8]> least-positive-short-float
-;;;   <Krystof> 2.93874s-39
-;;;   <Krystof> [9]> (coerce * 'single-float)
-;;;   <Krystof> 0.0
-;;;   <chandler> aah
-;;;   <mwh> "oops"
-;;;   <Krystof> yep
-;;;   <mwh> tried that on clisp from fink:
-;;;   <mwh> [1]> least-positive-short-float
-;;;   <mwh> 2.93874s-39
-;;;   <mwh> [2]> (coerce * 'single-float)
-;;;   <mwh> *** - floating point underflow
-;;;   <Krystof> yeah
-;;;   <mwh> shall i not try to build sbcl with that?
-;;;   <Krystof> if you turn off underflow traps, then you get 0.0
-;;;   <mwh> well, that makes sense, i guess
-;;;   <Krystof> #+clisp
-;;;   <Krystof> (ext:without-package-lock ("SYSTEM")
-;;;   <Krystof>   (setf system::*inhibit-floating-point-underflow* t))
-;;;   <Krystof> (in src/cold/ansify.lisp)
-#+clisp
-(ext:without-package-lock ("SYSTEM")
-  (setf system::*inhibit-floating-point-underflow* t))
-
 ;;;; CMU CL issues
 
 ;;; CMU CL, at least as of 18b, doesn't support PRINT-OBJECT. In
-- 
1.8.3.3