| blob | 9e4dcd3926c09848b91a03c404fc242ae68083b0 |
1 ;;;; permutation vectors
3 ;;;; This software is part of the SBCL system. See the README file for
4 ;;;; more information.
6 ;;;; This software is derived from software originally released by Xerox
7 ;;;; Corporation. Copyright and release statements follow. Later modifications
8 ;;;; to the software are in the public domain and are provided with
9 ;;;; absolutely no warranty. See the COPYING and CREDITS files for more
10 ;;;; information.
12 ;;;; copyright information from original PCL sources:
13 ;;;;
14 ;;;; Copyright (c) 1985, 1986, 1987, 1988, 1989, 1990 Xerox Corporation.
15 ;;;; All rights reserved.
16 ;;;;
17 ;;;; Use and copying of this software and preparation of derivative works based
18 ;;;; upon this software are permitted. Any distribution of this software or
19 ;;;; derivative works must comply with all applicable United States export
20 ;;;; control laws.
21 ;;;;
22 ;;;; This software is made available AS IS, and Xerox Corporation makes no
23 ;;;; warranty about the software, its performance or its conformity to any
24 ;;;; specification.
27 \f
35 \f
37 (:constructor make-pv-table-internal
47 ;;; FIXME: The comment below seem to indicate that this was intended
48 ;;; to be actually used, however, it isn't anymore, and was commented
49 ;;; out at 0.9.13.47. Also removed was code in MAKE-PV-TABLE that
50 ;;; pushed each new PV-TABLE onto this list. --NS 2006-06-18
51 ;;;
52 ;;; help new slot-value-using-class methods affect fast iv access
53 ;;;
54 ;;; (defvar *all-pv-table-list* nil)
66 ;;; Entries in this are lists of (table . pv-offset-list).
94 pv-table))))
120 nil)
130 ref)
131 \f
167 nil)
168 elements)))))))
172 #||
176 call-list)
177 ||#
178 '#())
194 wrappers classes types
198 ||#
210 :value t
214 value
219 ;; This is safe: if another thread races us here the loser just
220 ;; misses the next time as well.
223 pv-cell)))))
260 nil)))
261 slot-names))
265 slot-name
285 cwrapper pv-size pv-map))
286 cache))))))
305 \f
316 required-parameters))))
319 parameter-or-nil
320 env)))
333 ;;; Check whether the binding of the named variable is modified in the
334 ;;; method body.
346 slot-name nil)))))
347 ;; We don't return the optimized form directly, since there's
348 ;; still a chance that we'll find out later on that the
349 ;; optimization should not have been done, for example due to
350 ;; the walker encountering a SETQ on SPARAMETER later on in
351 ;; the body [ see for example clos.impure.lisp test with :name
352 ;; ((:setq :method-parameter) slot-value)) ]. Instead we defer
353 ;; the decision until the compiler macroexpands
354 ;; OPTIMIZED-SLOT-VALUE.
355 ;;
356 ;; Note that we must still call OPTIMIZE-INSTANCE-ACCESS at
357 ;; this point (instead of when expanding
358 ;; OPTIMIZED-SLOT-VALUE), since it mutates the structure of
359 ;; SLOTS. If that mutation isn't done during the walking,
360 ;; MAKE-METHOD-LAMBDA-INTERNAL won't wrap a correct PV-BINDING
361 ;; form around the body, and compilation will fail. -- JES,
362 ;; 2006-09-18
368 ;; Either use OPTIMIZED-FORM or fall back to the safe
369 ;; ACCESSOR-SLOT-VALUE.
372 optimized-form))
381 :write
382 sparameter
383 slot-name
384 new-value)))))
385 ;; See OPTIMIZE-SLOT-VALUE
392 ;; Don't optimize slot value setting in safe code, since the
393 ;; optimized version will fail to catch some type errors
394 ;; (for example when a subclass declares a tighter type for
395 ;; the slot than a superclass).
400 optimized-form)))
406 ;; FIXME: In CMU CL ca. 19991205, this binding list
407 ;; had a fourth element in it, NEW-VALUE. It's hard
408 ;; to see how that could possibly be right, since
409 ;; SLOT-BOUNDP has no NEW-VALUE. Since it was
410 ;; causing a failure in building PCL for SBCL, so I
411 ;; changed it to match the definition of
412 ;; SLOT-BOUNDP (and also to match the list used in
413 ;; the similar OPTIMIZE-SLOT-VALUE,
414 ;; above). However, I'm weirded out by this, since
415 ;; this is old code which has worked for ages to
416 ;; build PCL for CMU CL, so it's hard to see why it
417 ;; should need a patch like this in order to build
418 ;; PCL for SBCL. I'd like to return to this and
419 ;; find a test case which exercises this function
420 ;; both in CMU CL, to see whether it's really a
421 ;; previously-unexercised bug or whether I've
422 ;; misunderstood something (and, presumably,
423 ;; patched it wrong).
425 form
429 :boundp
430 sparameter
431 slot-name
432 nil)))))
433 ;; See OPTIMIZE-SLOT-VALUE
441 optimized-form))
443 ;;; The SLOTS argument is an alist, the CAR of each entry is the name
444 ;;; of a required parameter to the function. The alist is in order, so
445 ;;; the position of an entry in the alist corresponds to the
446 ;;; argument's position in the lambda list.
448 read/write
449 sparameter
450 slot-name
451 new-value)
459 (:read
461 (:write
465 (:boundp
466 t)))
478 (:read
481 (:write
485 (:boundp
494 ;;; It is safe for these two functions to be wrong. They just try to
495 ;;; guess what the most likely case will be.
515 slot-name
516 type))))))
528 default
534 ;; FIXME: the line marked by KLUDGE below
535 ;; (and the analogous spot in
536 ;; INSTANCE-WRITE-INTERNAL) is there purely
537 ;; to suppress a type mismatch warning that
538 ;; propagates through to user code.
539 ;; Presumably SLOTS at this point can never
540 ;; actually be NIL, but the compiler seems
541 ;; to think it could, so we put this here
542 ;; to shut it up. (see also mail Rudi
543 ;; Schlatte sbcl-devel 2003-09-21) -- CSR,
544 ;; 2003-11-30
553 ,default
569 default
583 parameter
584 position
585 slot-name
586 class
587 new-value)
601 default
622 ;;; This magic function has quite a job to do indeed.
623 ;;;
624 ;;; The careful reader will recall that <slots> contains all of the
625 ;;; optimized slot access forms produced by OPTIMIZE-INSTANCE-ACCESS.
626 ;;; Each of these is a call to either INSTANCE-READ or INSTANCE-WRITE.
627 ;;;
628 ;;; At the time these calls were produced, the first argument was
629 ;;; specified as the symbol .PV-OFFSET.; what we have to do now is
630 ;;; convert those pv-offset arguments into the actual number that is
631 ;;; the correct offset into the pv.
632 ;;;
633 ;;; But first, oh but first, we sort <slots> a bit so that for each
634 ;;; argument we have the slots in alphabetical order. This
635 ;;; canonicalizes the PV-TABLE's a bit and will hopefully lead to
636 ;;; having fewer PV's floating around. Even if the gain is only
637 ;;; modest, it costs nothing.
643 slots))
653 slot-name-lists))
658 slot-name-lists)))))
664 arg))
666 call-list)))
688 ;;; FIXME: Because of the existence of UNINTERN and RENAME-PACKAGE,
689 ;;; the part of this ordering which is based on SYMBOL-PKG-NAME is not
690 ;;; stable. This ordering is only used in to
691 ;;; SLOT-NAME-LISTS-FROM-SLOTS, where it serves to "canonicalize the
692 ;;; PV-TABLE's a bit and will hopefully lead to having fewer PV's
693 ;;; floating around", so it sounds as though the instability won't
694 ;;; actually lead to bugs, just small inefficiency. But still, it
695 ;;; would be better to reimplement this function as a comparison based
696 ;;; on SYMBOL-HASH:
697 ;;; * stable comparison
698 ;;; * smaller code (here, and in being able to discard SYMBOL-PKG-NAME)
699 ;;; * faster code.
723 #'symbol-or-cons-lessp
725 slots))
729 \f
730 ;;;; This needs to work in terms of metatypes and also needs to work
731 ;;;; for automatically generated reader and writer functions.
732 ;;;; Automatically generated reader and writer functions use this
733 ;;;; stuff too.
739 for required-parameter in required-parameters
740 for i from 0
752 slot-vars pv-parameters))
756 ;;; This will only be visible in PV-ENV when the default MAKE-METHOD-LAMBDA is
757 ;;; overridden.
763 ;; Decide which expansion to use based on the state of the PV-ENV-ENVIRONMENT
764 ;; symbol-macrolet.
782 ;; FIXME: VALUES was in this list, conditionalized with #+CMU, but I
783 ;; don't *think* CMU CL had, or SBCL has, VALUES declarations. If
784 ;; SBCL doesn't have 'em, VALUES should probably be removed from
785 ;; this list.
787 %method-name
788 %method-lambda-list
789 optimize
790 ftype
791 muffle-conditions
792 inline
793 notinline))
796 '(%class
797 type))
801 ignorable special dynamic-extent
802 ;; FIXME: Possibly this entire list and variable could go away.
803 ;; If not, certainly we should remove all these built-in typenames
804 ;; from the list, and replace them with a test for "is it a type
805 ;; name?" (CLTL1 allowed only built-in type names as declarations,
806 ;; but ANSI CL allows any type name as a declaration.)
807 array atom base-char bignum bit bit-vector character compiled-function
808 complex cons double-float extended-char
809 fixnum float function hash-table integer
810 keyword list long-float nil null number package pathname random-state ratio
811 rational readtable sequence short-float signed-byte simple-array
812 simple-bit-vector simple-string simple-vector single-float standard-char
813 stream string symbol t unsigned-byte vector))
818 decl)
838 ;; FIXME: This warning, and perhaps the
839 ;; various *VAR-DECLARATIONS-FOO* and/or
840 ;; *NON-VAR-DECLARATIONS* variables,
841 ;; could probably go away now that we're not
842 ;; trying to be portable between different
843 ;; CLTL1 hosts the way PCL was. (Note that to
844 ;; do this right, we need to be able to handle
845 ;; user-defined (DECLAIM (DECLARATION FOO))
846 ;; stuff.)
848 Please put ~S on one of the lists ~S,~%~S, or~%~S.~@
849 (Assuming it is a variable declaration without argument)."
850 declaration-name 'split-declarations
851 declaration-name
863 ;; Quietly remove IGNORE declarations
864 ;; on args when a next-method is
865 ;; involved, to prevent compiler
866 ;; warnings about ignored args being
867 ;; read.
877 inner-decls)))))))))
881 ;;; Pull a name out of the %METHOD-NAME declaration in the function
882 ;;; body given, or return NIL if no %METHOD-NAME declaration is found.
890 name)))))
892 ;;; Convert a lambda expression containing a SB-PCL::%METHOD-NAME
893 ;;; declaration (which is a naming style internal to PCL) into an
894 ;;; SB-INT:NAMED-LAMBDA expression (which is a naming style used
895 ;;; throughout SBCL, understood by the main compiler); or if there's
896 ;;; no SB-PCL::%METHOD-NAME declaration, then just return the original
897 ;;; lambda expression.
902 method-lambda)))
907 lmf ; becomes body of function
908 lmf-params)
937 ;; Given a valid lambda list, extract the parameter names.
939 with res = nil
944 ;; ... ((:BAR FOO) 1)
946 ;; ... (FOO 1)
948 ;; ... (... 1 FOO-P)
952 ;; ... FOO
960 ;; Names of the parameters that will be in the outermost lambda-list
961 ;; (and whose bound declarations thus need to be in OUTER-DECLS).
963 ;; The lambda-list used by BIND-ARGS
968 ;; Try to use the normal function call machinery instead of BIND-ARGS
969 ;; binding the arguments, unless:
971 ;; in any case.
973 ;; CALL-NEXT-METHOD wants to use BIND-ARGS, and needs a
974 ;; list of all non-required arguments.
975 call-next-method-p)
977 restp nil
978 ;; Get all the parameters for declaration parsing
980 ;; Ensure that BIND-ARGS won't do anything (since
981 ;; BIND-LIST won't contain any non-required parameters,
982 ;; and REQ-ARGS will be of an equal length). We still want
983 ;; to pass BIND-LIST to FAST-LEXICAL-METHOD-FUNCTIONS so
984 ;; that BIND-FAST-LEXICAL-METHOD-FUNCTIONS can take care
985 ;; of rebinding SETQd required arguments around the method
986 ;; body.
987 bind-list req-args))
996 req-args
997 lambda-list))))
999 :function
1002 ;; function name
1004 ;; The lambda-list of the FMF
1006 ;; body of the function
1009 ,@outer-decls
1014 ,@inner-decls
1019 mf)
1022 ;;; Use arrays and hash tables and the fngen stuff to make this much
1023 ;;; better. It doesn't really matter, though, because a function
1024 ;;; returned by this will get called only when the user explicitly
1025 ;;; funcalls a result of method-function. BUT, this is needed to make
1026 ;;; early methods work.
1047 nm)
1050 ;; FIXME: this looks dangerous.
1054 method-function))
1056 ;;; this is similar to the above, only not quite. Only called when
1057 ;;; the MOP is heavily involved. Not quite parallel to
1058 ;;; METHOD-FUNCTION-FROM-FAST-METHOD-FUNCTION, because we can close
1059 ;;; over the actual PV-CELL in this case.
1073 nm)
1091 wrapper)
1092 wrappers)))))
1096 when snl
1100 ;;; Return the subset of WRAPPERS which is used in the cache
1101 ;;; of PV-TABLE.
1104 when snl
1105 collect w into result