From 485d9c8e2d3a4ae0561cd57b55a6c6a28cd4bce4 Mon Sep 17 00:00:00 2001 From: William Harold Newman Date: Tue, 12 Sep 2006 13:11:46 +0000 Subject: [PATCH] 0.9.16.26: memory crutch for middle-aged maintainers: repeated NS's explanation in 0.9.16.25 commit message as comment above the change --- src/compiler/globaldb.lisp | 6 +++++- version.lisp-expr | 2 +- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/src/compiler/globaldb.lisp b/src/compiler/globaldb.lisp index 4aefaff..1f1eeb5 100644 --- a/src/compiler/globaldb.lisp +++ b/src/compiler/globaldb.lisp @@ -789,13 +789,17 @@ new-value) #!-sb-fluid (progn + ;; Not all xc hosts are happy about SETF compiler macros: CMUCL 19 + ;; does not accept them at all, and older SBCLs give a full warning. + ;; So the easy thing is to hide this optimization from all xc hosts. #-sb-xc-host (define-compiler-macro (setf info) (&whole whole new-value class type name - &optional (env-list nil env-list-p)) + &optional (env-list nil + env-list-p)) ;; Constant CLASS and TYPE is an overwhelmingly common special case, ;; and we can resolve it much more efficiently than the general ;; case. diff --git a/version.lisp-expr b/version.lisp-expr index a966c58..041ec82 100644 --- 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.9.16.25" +"0.9.16.26" -- 1.7.10.4