X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcode%2Ftarget-extensions.lisp;h=7b13df4cc126888d0391a406512bd9aa89c95937;hb=cd176690400f8b6fa23faa4dc6fa8494bcbce480;hp=adf1f84da200dcc7aebe2b3df8e51a153a2952d1;hpb=d45e8a2e9167150c8283783152d2449bd8d59d2d;p=sbcl.git

diff --git a/src/code/target-extensions.lisp b/src/code/target-extensions.lisp
index adf1f84..7b13df4 100644
--- a/src/code/target-extensions.lisp
+++ b/src/code/target-extensions.lisp
@@ -69,29 +69,3 @@
 	 :format-control "~@<~A: ~2I~_~A~:>"
 	 :format-arguments (list prefix-string (strerror errno))
 	 other-condition-args))
-
-;;;; optimization idioms
-
-(eval-when (:compile-toplevel :load-toplevel :execute)
-
-  ;; Byte compile this thing if possible.
-  (defvar *optimize-byte-compilation*
-    '(optimize (speed 0) (safety 1)))
-
-  ;; This thing is externally visible, so compiling meta-information
-  ;; is more important than byte-compiling it; but it's otherwise
-  ;; suitable for byte-compilation.
-  ;;
-  ;; (As long as the byte compiler isn't capable of compiling
-  ;; meta-information such as the argument list required by functions
-  ;; (as in sbcl-0.6.12, anyway), it's not suitable for compiling
-  ;; externally visible things like CL:INSPECT even if their speed
-  ;; requirements are small enough that it'd otherwise be OK. If some
-  ;; later version of the byte compiler learns to compile such
-  ;; meta-information, we'll probably change the implementation of
-  ;; this idiom so that it causes byte compilation of the thing after
-  ;; all.)
-  (defvar *optimize-external-despite-byte-compilation*
-    '(optimize (speed 1)
-	       ;; still might as well be as small as possible..
-	       (space 3))))