| blob | dcecc2eaa8246d443c96ba57377716ee37d850ad |
1 ;;;; This file contains compiler code and compiler-related stuff which
2 ;;;; can be built early on. Some of the stuff may be here because it's
3 ;;;; needed early on, some other stuff (e.g. constants) just because
4 ;;;; it might as well be done early so we don't have to think about
5 ;;;; whether it's done early enough.
7 ;;;; This software is part of the SBCL system. See the README file for
8 ;;;; more information.
9 ;;;;
10 ;;;; This software is derived from the CMU CL system, which was
11 ;;;; written at Carnegie Mellon University and released into the
12 ;;;; public domain. The software is in the public domain and is
13 ;;;; provided with absolutely no warranty. See the COPYING and CREDITS
14 ;;;; files for more information.
18 ;;; ANSI limits on compilation
20 #!+sb-doc
21 "The exclusive upper bound on the number of arguments which may be passed
24 #!+sb-doc
25 "The exclusive upper bound on the number of parameters which may be specified
26 in a given lambda list. This is actually the limit on required and &OPTIONAL
29 #!+sb-doc
30 "The exclusive upper bound on the number of multiple VALUES that you can
32 \f
33 ;;;; cross-compiler-only versions of CL special variables, so that we
34 ;;;; don't have weird interactions with the host compiler
40 \f
41 ;;;; miscellaneous types used both in the cross-compiler and on the target
43 ;;;; FIXME: The INDEX and LAYOUT-DEPTHOID definitions probably belong
44 ;;;; somewhere else, not "early-c", since they're after all not part
45 ;;;; of the compiler.
47 ;;; the type of LAYOUT-DEPTHOID slot values
49 \f
50 ;;; An INLINEP value describes how a function is called. The values
51 ;;; have these meanings:
52 ;;; NIL No declaration seen: do whatever you feel like, but don't
53 ;;; dump an inline expansion.
54 ;;; :NOTINLINE NOTINLINE declaration seen: always do full function call.
55 ;;; :INLINE INLINE declaration seen: save expansion, expanding to it
56 ;;; if policy favors.
57 ;;; :MAYBE-INLINE
58 ;;; Retain expansion, but only use it opportunistically.
59 ;;; :MAYBE-INLINE is quite different from :INLINE. As explained
60 ;;; by APD on #lisp 2005-11-26: "MAYBE-INLINE lambda is
61 ;;; instantiated once per component, INLINE - for all
62 ;;; references (even under #'without FUNCALL)."
70 ;;; *FREE-VARS* translates from the names of variables referenced
71 ;;; globally to the LEAF structures for them. *FREE-FUNS* is like
72 ;;; *FREE-VARS*, only it deals with function names.
77 ;;; We use the same CONSTANT structure to represent all equal anonymous
78 ;;; constants. This hashtable translates from constants to the LEAFs that
79 ;;; represent them.
83 ;;; *ALLOW-INSTRUMENTING* controls whether we should allow the
84 ;;; insertion of instrumenting code (like a (CATCH ...)) around code
85 ;;; to allow the debugger RETURN and STEP commands to function (we
86 ;;; disallow it for internal stuff).
89 ;;; miscellaneous forward declarations
110 #!+inline-constants
123 #!+sb-doc
124 "If true (the default), the compiler respects DYNAMIC-EXTENT declarations
125 and stack allocates otherwise inaccessible parts of the object whenever
126 possible. Potentially long (over one page in size) vectors are, however, not
127 stack allocated except in zero SAFETY code, as such a vector could overflow
131 ;;; This lock is seized in the compiler, and related areas -- like the
132 ;;; classoid/layout/class system.
134 (!cold-init-forms
145 ;;; unique ID for the next object created (to let us track object
146 ;;; identity even across GC, useful for understanding weird compiler
147 ;;; bugs where something is supposed to be unique but is instead
148 ;;; exists as duplicate objects)
149 #!+sb-show
156 \f
157 ;;;; miscellaneous utilities
159 ;;; This is for "observers" who want to know if type names have been added.
160 ;;; Rather than registering listeners, they can detect changes by comparing
161 ;;; their stored nonce to the current nonce. Additionally the observers
162 ;;; can detect whether function definitions have occurred.
167 #-no-ansi-print-object
172 ;; the name of the unknown thing
174 ;; the kind of reference to NAME
176 ;; the number of times this thing was used
178 ;; a list of COMPILER-ERROR-CONTEXT structures describing places
179 ;; where this thing was used. Note that we only record the first
180 ;; *UNDEFINED-WARNING-LIMIT* calls.
183 ;;; Delete any undefined warnings for NAME and KIND. This is for the
184 ;;; benefit of the compiler, but it's sometimes called from stuff like
185 ;;; type-defining code which isn't logically part of the compiler.
187 note-name-defined))
190 ;; We do this BOUNDP check because this function can be called when
191 ;; not in a compilation unit (as when loading top level forms).
200 ;;; to be called when a variable is lexically bound
203 ;; This check is intended to protect us from getting silently
204 ;; burned when we define
205 ;; foo.lisp:
206 ;; (DEFVAR *FOO* -3)
207 ;; (DEFUN FOO (X) (+ X *FOO*))
208 ;; bar.lisp:
209 ;; (DEFUN BAR (X)
210 ;; (LET ((*FOO* X))
211 ;; (FOO 14)))
212 ;; and then we happen to compile bar.lisp before foo.lisp.
214 ;; FIXME: should be COMPILER-STYLE-WARNING?
216 :format-control
217 "using the lexical binding of the symbol ~
218 ~/sb-impl::print-symbol-with-prefix/, not the~@
219 dynamic binding"
284 x)
291 name))))