X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fpcl%2Fcompiler-support.lisp;h=e00deee1111d1498d278580d633b2dd0ed0a8d8e;hb=1dc38285834db2d374a156a4f68b19096341deb3;hp=5cc7d3fdb0f7531df37b4e52b741e57dde4daab4;hpb=310aee0b439b715a5ec242862ab0a4d254e123b5;p=sbcl.git diff --git a/src/pcl/compiler-support.lisp b/src/pcl/compiler-support.lisp index 5cc7d3f..e00deee 100644 --- a/src/pcl/compiler-support.lisp +++ b/src/pcl/compiler-support.lisp @@ -98,3 +98,44 @@ new-value) (defsetf sb-pcl::random-documentation sb-pcl::set-random-documentation) + +;;;; SLOT-VALUE optimizations + +(defknown slot-value (t symbol) t (any)) +(defknown sb-pcl::set-slot-value (t symbol t) t (any)) + +(defun pcl-boot-state-complete-p () + (eq 'sb-pcl::complete sb-pcl::*boot-state*)) + +;;; These essentially duplicate what the compiler-macros in slots.lisp +;;; do, but catch more cases. We retain the compiler-macros since they +;;; can be used during the build, and because they catch common cases +;;; slightly more cheaply then the transforms. (Transforms add new +;;; lambdas, which requires more work by the compiler.) + +(deftransform slot-value ((object slot-name)) + "optimize" + (let (c-slot-name) + (if (and (pcl-boot-state-complete-p) + (constant-lvar-p slot-name) + (setf c-slot-name (lvar-value slot-name)) + (sb-pcl::interned-symbol-p c-slot-name)) + `(sb-pcl::accessor-slot-value object ',c-slot-name) + (give-up-ir1-transform "Slot name is not constant.")))) + +(deftransform sb-pcl::set-slot-value ((object slot-name new-value) + (t symbol t) t + ;; Safe code wants to check the + ;; type, and the global accessor + ;; won't do that. Also see the + ;; comment in the + ;; compiler-macro. + :policy (< safety 3)) + "optimize" + (let (c-slot-name) + (if (and (pcl-boot-state-complete-p) + (constant-lvar-p slot-name) + (setf c-slot-name (lvar-value slot-name)) + (sb-pcl::interned-symbol-p c-slot-name)) + `(sb-pcl::accessor-set-slot-value object ',c-slot-name new-value) + (give-up-ir1-transform "Slot name is not constant."))))