| blob | dc1f7c821b5c013a1207884d237be361ba5f25e0 |
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 ;;; the lexical environment we are currently converting in
74 ;;; *FREE-VARS* translates from the names of variables referenced
75 ;;; globally to the LEAF structures for them. *FREE-FUNS* is like
76 ;;; *FREE-VARS*, only it deals with function names.
81 ;;; We use the same CONSTANT structure to represent all equal anonymous
82 ;;; constants. This hashtable translates from constants to the LEAFs that
83 ;;; represent them.
87 ;;; *ALLOW-INSTRUMENTING* controls whether we should allow the
88 ;;; insertion of instrumenting code (like a (CATCH ...)) around code
89 ;;; to allow the debugger RETURN and STEP commands to function (we
90 ;;; disallow it for internal stuff).
93 ;;; miscellaneous forward declarations
118 #!+inline-constants
132 #!+sb-doc
133 "If true (the default), the compiler respects DYNAMIC-EXTENT declarations
134 and stack allocates otherwise inaccessible parts of the object whenever
135 possible. Potentially long (over one page in size) vectors are, however, not
136 stack allocated except in zero SAFETY code, as such a vector could overflow
140 ;;; This lock is seized in the compiler, and related areas -- like the
141 ;;; classoid/layout/class system.
143 (!cold-init-forms
154 ;;; unique ID for the next object created (to let us track object
155 ;;; identity even across GC, useful for understanding weird compiler
156 ;;; bugs where something is supposed to be unique but is instead
157 ;;; exists as duplicate objects)
158 #!+sb-show
165 \f
166 ;;;; miscellaneous utilities
168 ;;; Delete any undefined warnings for NAME and KIND. This is for the
169 ;;; benefit of the compiler, but it's sometimes called from stuff like
170 ;;; type-defining code which isn't logically part of the compiler.
172 note-name-defined))
174 ;; We do this BOUNDP check because this function can be called when
175 ;; not in a compilation unit (as when loading top level forms).
184 ;;; to be called when a variable is lexically bound
187 ;; This check is intended to protect us from getting silently
188 ;; burned when we define
189 ;; foo.lisp:
190 ;; (DEFVAR *FOO* -3)
191 ;; (DEFUN FOO (X) (+ X *FOO*))
192 ;; bar.lisp:
193 ;; (DEFUN BAR (X)
194 ;; (LET ((*FOO* X))
195 ;; (FOO 14)))
196 ;; and then we happen to compile bar.lisp before foo.lisp.
198 ;; FIXME: should be COMPILER-STYLE-WARNING?
200 :format-control
201 "using the lexical binding of the symbol ~
202 ~/sb-impl::print-symbol-with-prefix/, not the~@
203 dynamic binding"
267 x)
274 name))))