0.8.0.35:

	Compiler depessimization, (part IV of XL :-)
	... let's see what happens if we're a little less demure about
	putting derived function types into the globaldb.  We don't
	actually use them unless SB-EXT:*DERIVE-FUNCTION-TYPES* is true,
	so this shouldn't make a difference to the compiler in normal
	circumstances (though it does when the compiler is being built,
	and also can do for libraries who choose to use the extension)

	This is probably a staging post on the way to ANSI-style
	optimization of file-compilation, wherein we can treat all the
	functions in one file as tightly coupled (see CLHS 3.2.2.3)

diff --git a/src/compiler/ir1final.lisp b/src/compiler/ir1final.lisp
index 94240a0..8802d7e 100644 (file)
--- a/src/compiler/ir1final.lisp
+++ b/src/compiler/ir1final.lisp
@@ -86,8 +86,7 @@
                   (type-specifier declared-ftype)
                   (type-specifier defined-ftype)))))
            (:defined
-            (when global-p
-              (setf (info :function :type source-name) defined-ftype))))))))
+            (setf (info :function :type source-name) defined-ftype)))))))
   (values))
 
 ;;; Find all calls in COMPONENT to assumed functions and update the

diff --git a/version.lisp-expr b/version.lisp-expr
index 37dd033..6460a54 100644 (file)
--- a/version.lisp-expr
+++ b/version.lisp-expr
@@ -17,4 +17,4 @@
 ;;; checkins which aren't released. (And occasionally for internal
 ;;; versions, especially for internal versions off the main CVS
 ;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"0.8.0.34"
+"0.8.0.35"