1 ;;;; structures for the first intermediate representation in the
4 ;;;; This software is part of the SBCL system. See the README file for
7 ;;;; This software is derived from the CMU CL system, which was
8 ;;;; written at Carnegie Mellon University and released into the
9 ;;;; public domain. The software is in the public domain and is
10 ;;;; provided with absolutely no warranty. See the COPYING and CREDITS
11 ;;;; files for more information.
15 ;;; The front-end data structure (IR1) is composed of nodes and
16 ;;; continuations. The general idea is that continuations contain
17 ;;; top-down information and nodes contain bottom-up, derived
18 ;;; information. A continuation represents a place in the code, while
19 ;;; a node represents code that does something.
21 ;;; This representation is more of a flow-graph than an augmented
22 ;;; syntax tree. The evaluation order is explicitly represented in the
23 ;;; linkage by continuations, rather than being implicit in the nodes
24 ;;; which receive the the results of evaluation. This allows us to
25 ;;; decouple the flow of results from the flow of control. A
26 ;;; continuation represents both, but the continuation can represent
27 ;;; the case of a discarded result by having no DEST.
29 (def!struct (continuation
30 (:make-load-form-fun ignore-it)
31 (:constructor make-continuation (&optional dest)))
32 ;; an indication of the way that this continuation is currently used
35 ;; A continuation for which all control-related slots have the
36 ;; default values. A continuation is unused during IR1 conversion
37 ;; until it is assigned a block, and may be also be temporarily
38 ;; unused during later manipulations of IR1. In a consistent
39 ;; state there should never be any mention of :UNUSED
40 ;; continuations. Next can have a non-null value if the next node
41 ;; has already been determined.
44 ;; A continuation that has been deleted from IR1. Any pointers into
45 ;; IR1 are cleared. There are two conditions under which a deleted
46 ;; continuation may appear in code:
47 ;; -- The CONT of the LAST node in a block may be a deleted
48 ;; continuation when the original receiver of the continuation's
49 ;; value was deleted. Note that DEST in a deleted continuation is
50 ;; null, so it is easy to know not to attempt delivering any
51 ;; values to the continuation.
52 ;; -- Unreachable code that hasn't been deleted yet may receive
53 ;; deleted continuations. All such code will be in blocks that
54 ;; have DELETE-P set. All unreachable code is deleted by control
55 ;; optimization, so the backend doesn't have to worry about this.
58 ;; The continuation that is the START of BLOCK. This is the only kind
59 ;; of continuation that can have more than one use. The BLOCK's
60 ;; START-USES is a list of all the uses.
62 ;; :DELETED-BLOCK-START
63 ;; Like :BLOCK-START, but BLOCK has been deleted. A block
64 ;; starting continuation is made into a deleted block start when
65 ;; the block is deleted, but the continuation still may have
66 ;; value semantics. Since there isn't any code left, next is
70 ;; A continuation that is the CONT of some node in BLOCK.
71 (kind :unused :type (member :unused :deleted :inside-block :block-start
72 :deleted-block-start))
73 ;; The node which receives this value, if any. In a deleted
74 ;; continuation, this is null even though the node that receives
75 ;; this continuation may not yet be deleted.
76 (dest nil :type (or node null))
77 ;; If this is a NODE, then it is the node which is to be evaluated
78 ;; next. This is always null in :DELETED and :UNUSED continuations,
79 ;; and will be null in a :INSIDE-BLOCK continuation when this is the
81 (next nil :type (or node null))
82 ;; an assertion on the type of this continuation's value
83 (asserted-type *wild-type* :type ctype)
84 ;; cached type of this continuation's value. If NIL, then this must
85 ;; be recomputed: see CONTINUATION-DERIVED-TYPE.
86 (%derived-type nil :type (or ctype null))
87 ;; the node where this continuation is used, if unique. This is always
88 ;; null in :DELETED and :UNUSED continuations, and is never null in
89 ;; :INSIDE-BLOCK continuations. In a :BLOCK-START continuation, the
90 ;; Block's START-USES indicate whether NIL means no uses or more
92 (use nil :type (or node null))
93 ;; the basic block this continuation is in. This is null only in
94 ;; :DELETED and :UNUSED continuations. Note that blocks that are
95 ;; unreachable but still in the DFO may receive deleted
96 ;; continuations, so it isn't o.k. to assume that any continuation
97 ;; that you pick up out of its DEST node has a BLOCK.
98 (block nil :type (or cblock null))
99 ;; set to true when something about this continuation's value has
100 ;; changed. See REOPTIMIZE-CONTINUATION. This provides a way for IR1
101 ;; optimize to determine which operands to a node have changed. If
102 ;; the optimizer for this node type doesn't care, it can elect not
103 ;; to clear this flag.
104 (reoptimize t :type boolean)
105 ;; an indication of what we have proven about how this contination's
106 ;; type assertion is satisfied:
109 ;; No type check is necessary (proven type is a subtype of the assertion.)
112 ;; A type check is needed.
115 ;; Don't do a type check, but believe (intersect) the assertion.
116 ;; A T check can be changed to :DELETED if we somehow prove the
117 ;; check is unnecessary, or if we eliminate it through a policy
121 ;; Type check generation sets the slot to this if a check is
122 ;; called for, but it believes it has proven that the check won't
123 ;; be done for policy reasons or because a safe implementation
124 ;; will be used. In the latter case, LTN must ensure that a safe
125 ;; implementation *is* used.
128 ;; There is a compile-time type error in some use of this
129 ;; continuation. A type check should still be generated, but be
132 ;; This is computed lazily by CONTINUATION-DERIVED-TYPE, so use
133 ;; CONTINUATION-TYPE-CHECK instead of the %'ed slot accessor.
134 (%type-check t :type (member t nil :deleted :no-check :error))
135 ;; something or other that the back end annotates this continuation with
137 ;; uses of this continuation in the lexical environment. They are
138 ;; recorded so that when one continuation is substituted for another
139 ;; the environment may be updated properly.
140 (lexenv-uses nil :type list))
142 (def!method print-object ((x continuation) stream)
143 (print-unreadable-object (x stream :type t :identity t)))
145 (defstruct (node (:constructor nil)
147 ;; the bottom-up derived type for this node. This does not take into
148 ;; consideration output type assertions on this node (actually on its CONT).
149 (derived-type *wild-type* :type ctype)
150 ;; True if this node needs to be optimized. This is set to true
151 ;; whenever something changes about the value of a continuation
152 ;; whose DEST is this node.
153 (reoptimize t :type boolean)
154 ;; the continuation which receives the value of this node. This also
155 ;; indicates what we do controlwise after evaluating this node. This
156 ;; may be null during IR1 conversion.
157 (cont nil :type (or continuation null))
158 ;; the continuation that this node is the next of. This is null
159 ;; during IR1 conversion when we haven't linked the node in yet or
160 ;; in nodes that have been deleted from the IR1 by UNLINK-NODE.
161 (prev nil :type (or continuation null))
162 ;; the lexical environment this node was converted in
163 (lexenv *lexenv* :type lexenv)
164 ;; a representation of the source code responsible for generating
167 ;; For a form introduced by compilation (does not appear in the
168 ;; original source), the path begins with a list of all the
169 ;; enclosing introduced forms. This list is from the inside out,
170 ;; with the form immediately responsible for this node at the head
173 ;; Following the introduced forms is a representation of the
174 ;; location of the enclosing original source form. This transition
175 ;; is indicated by the magic ORIGINAL-SOURCE-START marker. The first
176 ;; element of the original source is the "form number", which is the
177 ;; ordinal number of this form in a depth-first, left-to-right walk
178 ;; of the truly-top-level form in which this appears.
180 ;; Following is a list of integers describing the path taken through
181 ;; the source to get to this point:
182 ;; (K L M ...) => (NTH K (NTH L (NTH M ...)))
184 ;; The last element in the list is the top level form number, which
185 ;; is the ordinal number (in this call to the compiler) of the truly
186 ;; top level form containing the original source.
187 (source-path *current-path* :type list)
188 ;; If this node is in a tail-recursive position, then this is set to
189 ;; T. At the end of IR1 (in physical environment analysis) this is
190 ;; computed for all nodes (after cleanup code has been emitted).
191 ;; Before then, a non-null value indicates that IR1 optimization has
192 ;; converted a tail local call to a direct transfer.
194 ;; If the back-end breaks tail-recursion for some reason, then it
195 ;; can null out this slot.
196 (tail-p nil :type boolean))
198 ;;; Flags that are used to indicate various things about a block, such
199 ;;; as what optimizations need to be done on it:
200 ;;; -- REOPTIMIZE is set when something interesting happens the uses of a
201 ;;; continuation whose Dest is in this block. This indicates that the
202 ;;; value-driven (forward) IR1 optimizations should be done on this block.
203 ;;; -- FLUSH-P is set when code in this block becomes potentially flushable,
204 ;;; usually due to a continuation's DEST becoming null.
205 ;;; -- TYPE-CHECK is true when the type check phase should be run on this
206 ;;; block. IR1 optimize can introduce new blocks after type check has
207 ;;; already run. We need to check these blocks, but there is no point in
208 ;;; checking blocks we have already checked.
209 ;;; -- DELETE-P is true when this block is used to indicate that this block
210 ;;; has been determined to be unreachable and should be deleted. IR1
211 ;;; phases should not attempt to examine or modify blocks with DELETE-P
212 ;;; set, since they may:
213 ;;; - be in the process of being deleted, or
214 ;;; - have no successors, or
215 ;;; - receive :DELETED continuations.
216 ;;; -- TYPE-ASSERTED, TEST-MODIFIED
217 ;;; These flags are used to indicate that something in this block
218 ;;; might be of interest to constraint propagation. TYPE-ASSERTED
219 ;;; is set when a continuation type assertion is strengthened.
220 ;;; TEST-MODIFIED is set whenever the test for the ending IF has
221 ;;; changed (may be true when there is no IF.)
222 (def-boolean-attribute block
223 reoptimize flush-p type-check delete-p type-asserted test-modified)
225 ;;; FIXME: Tweak so that definitions of e.g. BLOCK-DELETE-P is
226 ;;; findable by grep for 'def.*block-delete-p'.
227 (macrolet ((frob (slot)
228 `(defmacro ,(symbolicate "BLOCK-" slot) (block)
229 `(block-attributep (block-flags ,block) ,',slot))))
235 (frob test-modified))
237 ;;; The CBLOCK structure represents a basic block. We include
238 ;;; SSET-ELEMENT so that we can have sets of blocks. Initially the
239 ;;; SSET-ELEMENT-NUMBER is null, DFO analysis numbers in reverse DFO.
240 ;;; During IR2 conversion, IR1 blocks are re-numbered in forward emit
241 ;;; order. This latter numbering also forms the basis of the block
242 ;;; numbering in the debug-info (though that is relative to the start
243 ;;; of the function.)
244 (defstruct (cblock (:include sset-element)
245 (:constructor make-block (start))
246 (:constructor make-block-key)
249 (:copier copy-block))
250 ;; a list of all the blocks that are predecessors/successors of this
251 ;; block. In well-formed IR1, most blocks will have one successor.
252 ;; The only exceptions are:
253 ;; 1. component head blocks (any number)
254 ;; 2. blocks ending in an IF (1 or 2)
255 ;; 3. blocks with DELETE-P set (zero)
256 (pred nil :type list)
257 (succ nil :type list)
258 ;; the continuation which heads this block (either a :BLOCK-START or
259 ;; :DELETED-BLOCK-START), or NIL when we haven't made the start
260 ;; continuation yet (and in the dummy component head and tail
262 (start nil :type (or continuation null))
263 ;; a list of all the nodes that have START as their CONT
264 (start-uses nil :type list)
265 ;; the last node in this block. This is NIL when we are in the
266 ;; process of building a block (and in the dummy component head and
268 (last nil :type (or node null))
269 ;; the forward and backward links in the depth-first ordering of the
270 ;; blocks. These slots are NIL at beginning/end.
271 (next nil :type (or null cblock))
272 (prev nil :type (or null cblock))
273 ;; This block's attributes: see above.
274 (flags (block-attributes reoptimize flush-p type-check type-asserted
277 ;; CMU CL had a KILL slot here, documented as "set used by
278 ;; constraint propagation", which was used in constraint propagation
279 ;; as a list of LAMBDA-VARs killed, and in copy propagation as an
280 ;; SSET, representing I dunno what. I (WHN) found this confusing,
281 ;; and furthermore it caused type errors when I was trying to make
282 ;; the compiler produce fully general LAMBDA functions directly
283 ;; (instead of doing as CMU CL always did, producing extra little
284 ;; functions which return the LAMDBA you need) and therefore taking
285 ;; a new path through the compiler. So I split this into two:
286 ;; KILL-LIST = list of LAMBDA-VARs killed, used in constraint propagation
287 ;; KILL-SSET = an SSET value, used in copy propagation
288 (kill-list nil :type list)
289 (kill-sset nil :type (or sset null))
290 ;; other sets used in constraint propagation and/or copy propagation
294 ;; the component this block is in, or NIL temporarily during IR1
295 ;; conversion and in deleted blocks
297 (aver-live-component *current-component*)
299 :type (or component null))
300 ;; a flag used by various graph-walking code to determine whether
301 ;; this block has been processed already or what. We make this
302 ;; initially NIL so that FIND-INITIAL-DFO doesn't have to scan the
303 ;; entire initial component just to clear the flags.
305 ;; some kind of info used by the back end
307 ;; If true, then constraints that hold in this block and its
308 ;; successors by merit of being tested by its IF predecessor.
309 (test-constraint nil :type (or sset null)))
310 (def!method print-object ((cblock cblock) stream)
311 (print-unreadable-object (cblock stream :type t :identity t)
312 (format stream ":START c~W" (cont-num (block-start cblock)))))
314 ;;; The BLOCK-ANNOTATION class is inherited (via :INCLUDE) by
315 ;;; different BLOCK-INFO annotation structures so that code
316 ;;; (specifically control analysis) can be shared.
317 (defstruct (block-annotation (:constructor nil)
319 ;; The IR1 block that this block is in the INFO for.
320 (block (missing-arg) :type cblock)
321 ;; the next and previous block in emission order (not DFO). This
322 ;; determines which block we drop though to, and is also used to
323 ;; chain together overflow blocks that result from splitting of IR2
324 ;; blocks in lifetime analysis.
325 (next nil :type (or block-annotation null))
326 (prev nil :type (or block-annotation null)))
328 ;;; A COMPONENT structure provides a handle on a connected piece of
329 ;;; the flow graph. Most of the passes in the compiler operate on
330 ;;; COMPONENTs rather than on the entire flow graph.
332 ;;; According to the CMU CL internals/front.tex, the reason for
333 ;;; separating compilation into COMPONENTs is
334 ;;; to increase the efficiency of large block compilations. In
335 ;;; addition to improving locality of reference and reducing the
336 ;;; size of flow analysis problems, this allows back-end data
337 ;;; structures to be reclaimed after the compilation of each
339 (defstruct (component (:copier nil))
340 ;; the kind of component
342 ;; (The terminology here is left over from before
343 ;; sbcl-0.pre7.34.flaky5.2, when there was no such thing as
344 ;; FUNCTIONAL-HAS-EXTERNAL-REFERENCES-P, so that Python was
345 ;; incapable of building standalone :EXTERNAL functions, but instead
346 ;; had to implement things like #'CL:COMPILE as FUNCALL of a little
347 ;; toplevel stub whose sole purpose was to return an :EXTERNAL
350 ;; The possibilities are:
352 ;; an ordinary component, containing non-top-level code
354 ;; a component containing only load-time code
356 ;; In the old system, before FUNCTIONAL-HAS-EXTERNAL-REFERENCES-P
357 ;; was defined, this was necessarily a component containing both
358 ;; top level and run-time code. Now this state is also used for
359 ;; a component with HAS-EXTERNAL-REFERENCES-P functionals in it.
361 ;; the result of initial IR1 conversion, on which component
362 ;; analysis has not been done
364 ;; debris left over from component analysis
366 ;; See also COMPONENT-TOPLEVELISH-P.
367 (kind nil :type (member nil :toplevel :complex-toplevel :initial :deleted))
368 ;; the blocks that are the dummy head and tail of the DFO
370 ;; Entry/exit points have these blocks as their
371 ;; predecessors/successors. Null temporarily. The start and return
372 ;; from each non-deleted function is linked to the component head
373 ;; and tail. Until physical environment analysis links NLX entry
374 ;; stubs to the component head, every successor of the head is a
375 ;; function start (i.e. begins with a BIND node.)
376 (head nil :type (or null cblock))
377 (tail nil :type (or null cblock))
378 ;; This becomes a list of the CLAMBDA structures for all functions
379 ;; in this component. OPTIONAL-DISPATCHes are represented only by
380 ;; their XEP and other associated lambdas. This doesn't contain any
381 ;; deleted or LET lambdas.
383 ;; Note that logical associations between CLAMBDAs and COMPONENTs
384 ;; seem to exist for a while before this is initialized. See e.g.
385 ;; the NEW-FUNS slot. In particular, I got burned by writing some
386 ;; code to use this value to decide which components need
387 ;; LOCALL-ANALYZE-COMPONENT, when it turns out that
388 ;; LOCALL-ANALYZE-COMPONENT had a role in initializing this value
389 ;; (and DFO stuff does too, maybe). Also, even after it's
390 ;; initialized, it might change as CLAMBDAs are deleted or merged.
392 (lambdas () :type list)
393 ;; a list of FUNCTIONALs for functions that are newly converted, and
394 ;; haven't been local-call analyzed yet. Initially functions are not
395 ;; in the LAMBDAS list. Local call analysis moves them there
396 ;; (possibly as LETs, or implicitly as XEPs if an OPTIONAL-DISPATCH.)
397 ;; Between runs of local call analysis there may be some debris of
398 ;; converted or even deleted functions in this list.
399 (new-funs () :type list)
400 ;; If this is true, then there is stuff in this component that could
401 ;; benefit from further IR1 optimization.
402 (reoptimize t :type boolean)
403 ;; If this is true, then the control flow in this component was
404 ;; messed up by IR1 optimizations, so the DFO should be recomputed.
405 (reanalyze nil :type boolean)
406 ;; some sort of name for the code in this component
407 (name "<unknown>" :type simple-string)
408 ;; When I am a child, this is :NO-IR2-YET.
409 ;; In my adulthood, IR2 stores notes to itself here.
410 ;; After I have left the great wheel and am staring into the GC, this
411 ;; is set to :DEAD to indicate that it's a gruesome error to operate
412 ;; on me (e.g. by using me as *CURRENT-COMPONENT*, or by pushing
413 ;; LAMBDAs onto my NEW-FUNS, as in sbcl-0.pre7.115).
414 (info :no-ir2-yet :type (or ir2-component (member :no-ir2-yet :dead)))
415 ;; the SOURCE-INFO structure describing where this component was
417 (source-info *source-info* :type source-info)
418 ;; count of the number of inline expansions we have done while
419 ;; compiling this component, to detect infinite or exponential
421 (inline-expansions 0 :type index)
422 ;; a map from combination nodes to things describing how an
423 ;; optimization of the node failed. The description is an alist
424 ;; (TRANSFORM . ARGS), where TRANSFORM is the structure describing
425 ;; the transform that failed, and ARGS is either a list of format
426 ;; arguments for the note, or the FUN-TYPE that would have
427 ;; enabled the transformation but failed to match.
428 (failed-optimizations (make-hash-table :test 'eq) :type hash-table)
429 ;; This is similar to NEW-FUNS, but is used when a function has
430 ;; already been analyzed, but new references have been added by
431 ;; inline expansion. Unlike NEW-FUNS, this is not disjoint from
432 ;; COMPONENT-LAMBDAS.
433 (reanalyze-funs nil :type list))
434 (defprinter (component :identity t)
436 (reanalyze :test reanalyze))
438 ;;; Check that COMPONENT is suitable for roles which involve adding
439 ;;; new code. (gotta love imperative programming with lotso in-place
441 (defun aver-live-component (component)
442 ;; FIXME: As of sbcl-0.pre7.115, we're asserting that
443 ;; COMPILE-COMPONENT hasn't happened yet. Might it be even better
444 ;; (certainly stricter, possibly also correct...) to assert that
445 ;; IR1-FINALIZE hasn't happened yet?
446 (aver (not (eql (component-info component) :dead))))
448 ;;; Before sbcl-0.7.0, there were :TOPLEVEL things which were magical
449 ;;; in multiple ways. That's since been refactored into the orthogonal
450 ;;; properties "optimized for locall with no arguments" and "externally
451 ;;; visible/referenced (so don't delete it)". The code <0.7.0 did a lot
452 ;;; of tests a la (EQ KIND :TOP_LEVEL) in the "don't delete it?" sense;
453 ;;; this function is a sort of literal translation of those tests into
456 ;;; FIXME: After things settle down, bare :TOPLEVEL might go away, at
457 ;;; which time it might be possible to replace the COMPONENT-KIND
458 ;;; :TOPLEVEL mess with a flag COMPONENT-HAS-EXTERNAL-REFERENCES-P
459 ;;; along the lines of FUNCTIONAL-HAS-EXTERNAL-REFERENCES-P.
460 (defun lambda-toplevelish-p (clambda)
461 (or (eql (lambda-kind clambda) :toplevel)
462 (lambda-has-external-references-p clambda)))
463 (defun component-toplevelish-p (component)
464 (member (component-kind component)
465 '(:toplevel :complex-toplevel)))
467 ;;; A CLEANUP structure represents some dynamic binding action. Blocks
468 ;;; are annotated with the current CLEANUP so that dynamic bindings
469 ;;; can be removed when control is transferred out of the binding
470 ;;; environment. We arrange for changes in dynamic bindings to happen
471 ;;; at block boundaries, so that cleanup code may easily be inserted.
472 ;;; The "mess-up" action is explicitly represented by a funny function
473 ;;; call or ENTRY node.
475 ;;; We guarantee that CLEANUPs only need to be done at block boundaries
476 ;;; by requiring that the exit continuations initially head their
477 ;;; blocks, and then by not merging blocks when there is a cleanup
479 (defstruct (cleanup (:copier nil))
480 ;; the kind of thing that has to be cleaned up
482 :type (member :special-bind :catch :unwind-protect :block :tagbody))
483 ;; the node that messes things up. This is the last node in the
484 ;; non-messed-up environment. Null only temporarily. This could be
485 ;; deleted due to unreachability.
486 (mess-up nil :type (or node null))
487 ;; a list of all the NLX-INFO structures whose NLX-INFO-CLEANUP is
488 ;; this cleanup. This is filled in by physical environment analysis.
489 (nlx-info nil :type list))
490 (defprinter (cleanup :identity t)
493 (nlx-info :test nlx-info))
495 ;;; A PHYSENV represents the result of physical environment analysis.
497 ;;; As far as I can tell from reverse engineering, this IR1 structure
498 ;;; represents the physical environment (which is probably not the
499 ;;; standard Lispy term for this concept, but I dunno what is the
500 ;;; standard term): those things in the lexical environment which a
501 ;;; LAMBDA actually interacts with. Thus in
502 ;;; (DEFUN FROB-THINGS (THINGS)
503 ;;; (DOLIST (THING THINGS)
504 ;;; (BLOCK FROBBING-ONE-THING
505 ;;; (MAPCAR (LAMBDA (PATTERN)
506 ;;; (WHEN (FITS-P THING PATTERN)
507 ;;; (RETURN-FROM FROB-THINGS (LIST :FIT THING PATTERN))))
509 ;;; the variables THINGS, THING, and PATTERN and the block names
510 ;;; FROB-THINGS and FROBBING-ONE-THING are all in the inner LAMBDA's
511 ;;; lexical environment, but of those only THING, PATTERN, and
512 ;;; FROB-THINGS are in its physical environment. In IR1, we largely
513 ;;; just collect the names of these things; in IR2 an IR2-PHYSENV
514 ;;; structure is attached to INFO and used to keep track of
515 ;;; associations between these names and less-abstract things (like
516 ;;; TNs, or eventually stack slots and registers). -- WHN 2001-09-29
517 (defstruct (physenv (:copier nil))
518 ;; the function that allocates this physical environment
519 (lambda (missing-arg) :type clambda :read-only t)
520 #| ; seems not to be used as of sbcl-0.pre7.51
521 ;; a list of all the lambdas that allocate variables in this
522 ;; physical environment
523 (lambdas nil :type list)
525 ;; This ultimately converges to a list of all the LAMBDA-VARs and
526 ;; NLX-INFOs needed from enclosing environments by code in this
527 ;; physical environment. In the meantime, it may be
528 ;; * NIL at object creation time
529 ;; * a superset of the correct result, generated somewhat later
530 ;; * smaller and smaller sets converging to the correct result as
531 ;; we notice and delete unused elements in the superset
532 (closure nil :type list)
533 ;; a list of NLX-INFO structures describing all the non-local exits
534 ;; into this physical environment
535 (nlx-info nil :type list)
536 ;; some kind of info used by the back end
538 (defprinter (physenv :identity t)
540 (closure :test closure)
541 (nlx-info :test nlx-info))
543 ;;; An TAIL-SET structure is used to accumulate information about
544 ;;; tail-recursive local calls. The "tail set" is effectively the
545 ;;; transitive closure of the "is called tail-recursively by"
548 ;;; All functions in the same tail set share the same TAIL-SET
549 ;;; structure. Initially each function has its own TAIL-SET, but when
550 ;;; IR1-OPTIMIZE-RETURN notices a tail local call, it joins the tail
551 ;;; sets of the called function and the calling function.
553 ;;; The tail set is somewhat approximate, because it is too early to
554 ;;; be sure which calls will be tail-recursive. Any call that *might*
555 ;;; end up tail-recursive causes TAIL-SET merging.
556 (defstruct (tail-set)
557 ;; a list of all the LAMBDAs in this tail set
558 (funs nil :type list)
559 ;; our current best guess of the type returned by these functions.
560 ;; This is the union across all the functions of the return node's
561 ;; RESULT-TYPE, excluding local calls.
562 (type *wild-type* :type ctype)
563 ;; some info used by the back end
565 (defprinter (tail-set :identity t)
570 ;;; The NLX-Info structure is used to collect various information
571 ;;; about non-local exits. This is effectively an annotation on the
572 ;;; CONTINUATION, although it is accessed by searching in the
573 ;;; PHYSENV-NLX-INFO.
574 (def!struct (nlx-info (:make-load-form-fun ignore-it))
575 ;; the cleanup associated with this exit. In a catch or
576 ;; unwind-protect, this is the :CATCH or :UNWIND-PROTECT cleanup,
577 ;; and not the cleanup for the escape block. The CLEANUP-KIND of
578 ;; this thus provides a good indication of what kind of exit is
580 (cleanup (missing-arg) :type cleanup)
581 ;; the continuation exited to (the CONT of the EXIT nodes). If this
582 ;; exit is from an escape function (CATCH or UNWIND-PROTECT), then
583 ;; physical environment analysis deletes the escape function and
584 ;; instead has the %NLX-ENTRY use this continuation.
586 ;; This slot is primarily an indication of where this exit delivers
587 ;; its values to (if any), but it is also used as a sort of name to
588 ;; allow us to find the NLX-Info that corresponds to a given exit.
589 ;; For this purpose, the Entry must also be used to disambiguate,
590 ;; since exits to different places may deliver their result to the
591 ;; same continuation.
592 (continuation (missing-arg) :type continuation)
593 ;; the entry stub inserted by physical environment analysis. This is
594 ;; a block containing a call to the %NLX-Entry funny function that
595 ;; has the original exit destination as its successor. Null only
597 (target nil :type (or cblock null))
598 ;; some kind of info used by the back end
600 (defprinter (nlx-info :identity t)
607 ;;; Variables, constants and functions are all represented by LEAF
608 ;;; structures. A reference to a LEAF is indicated by a REF node. This
609 ;;; allows us to easily substitute one for the other without actually
610 ;;; hacking the flow graph.
611 (def!struct (leaf (:make-load-form-fun ignore-it)
613 ;; (For public access to this slot, use LEAF-SOURCE-NAME.)
615 ;; the name of LEAF as it appears in the source, e.g. 'FOO or '(SETF
616 ;; FOO) or 'N or '*Z*, or the special .ANONYMOUS. value if there's
617 ;; no name for this thing in the source (as can happen for
618 ;; FUNCTIONALs, e.g. for anonymous LAMBDAs or for functions for
619 ;; top-level forms; and can also happen for anonymous constants) or
620 ;; perhaps also if the match between the name and the thing is
621 ;; skewed enough (e.g. for macro functions or method functions) that
622 ;; we don't want to have that name affect compilation
624 ;; The value of this slot in can affect ordinary runtime behavior,
625 ;; e.g. of special variables and known functions, not just debugging.
627 ;; See also the LEAF-DEBUG-NAME function and the
628 ;; FUNCTIONAL-%DEBUG-NAME slot.
629 (%source-name (missing-arg)
630 :type (or symbol (and cons (satisfies legal-fun-name-p)))
632 ;; the type which values of this leaf must have
633 (type *universal-type* :type ctype)
634 ;; where the TYPE information came from:
635 ;; :DECLARED, from a declaration.
636 ;; :ASSUMED, from uses of the object.
637 ;; :DEFINED, from examination of the definition.
638 ;; FIXME: This should be a named type. (LEAF-WHERE-FROM? Or
639 ;; perhaps just WHERE-FROM, since it's not just used in LEAF,
640 ;; but also in various DEFINE-INFO-TYPEs in globaldb.lisp,
641 ;; and very likely elsewhere too.)
642 (where-from :assumed :type (member :declared :assumed :defined))
643 ;; list of the REF nodes for this leaf
645 ;; true if there was ever a REF or SET node for this leaf. This may
646 ;; be true when REFS and SETS are null, since code can be deleted.
647 (ever-used nil :type boolean)
648 ;; some kind of info used by the back end
651 ;;; LEAF name operations
653 ;;; KLUDGE: wants CLOS..
654 (defun leaf-has-source-name-p (leaf)
655 (not (eq (leaf-%source-name leaf)
657 (defun leaf-source-name (leaf)
658 (aver (leaf-has-source-name-p leaf))
659 (leaf-%source-name leaf))
660 (defun leaf-debug-name (leaf)
661 (if (functional-p leaf)
662 ;; FUNCTIONALs have additional %DEBUG-NAME behavior.
663 (functional-debug-name leaf)
664 ;; Other objects just use their source name.
666 ;; (As of sbcl-0.pre7.85, there are a few non-FUNCTIONAL
667 ;; anonymous objects, (anonymous constants..) and those would
668 ;; fail here if we ever tried to get debug names from them, but
669 ;; it looks as though it's never interesting to get debug names
670 ;; from them, so it's moot. -- WHN)
671 (leaf-source-name leaf)))
673 ;;; The CONSTANT structure is used to represent known constant values.
674 ;;; If NAME is not null, then it is the name of the named constant
675 ;;; which this leaf corresponds to, otherwise this is an anonymous
677 (def!struct (constant (:include leaf))
678 ;; the value of the constant
680 (defprinter (constant :identity t)
681 (%source-name :test %source-name)
684 ;;; The BASIC-VAR structure represents information common to all
685 ;;; variables which don't correspond to known local functions.
686 (def!struct (basic-var (:include leaf)
688 ;; Lists of the set nodes for this variable.
689 (sets () :type list))
691 ;;; The GLOBAL-VAR structure represents a value hung off of the symbol
692 ;;; NAME. We use a :CONSTANT VAR when we know that the thing is a
693 ;;; constant, but don't know what the value is at compile time.
694 (def!struct (global-var (:include basic-var))
695 ;; kind of variable described
697 :type (member :special :global-function :global)))
698 (defprinter (global-var :identity t)
700 (type :test (not (eq type *universal-type*)))
701 (where-from :test (not (eq where-from :assumed)))
704 ;;; The SLOT-ACCESSOR structure represents slot accessor functions. It
705 ;;; is a subtype of GLOBAL-VAR to make it look more like a normal
707 (def!struct (slot-accessor (:include global-var
708 (where-from :defined)
709 (kind :global-function)))
710 ;; The description of the structure that this is an accessor for.
711 (for (missing-arg) :type sb!xc:class)
712 ;; The slot description of the slot.
713 (slot (missing-arg)))
714 (defprinter (slot-accessor :identity t)
719 ;;; A DEFINED-FUN represents a function that is defined in the same
720 ;;; compilation block, or that has an inline expansion, or that has a
721 ;;; non-NIL INLINEP value. Whenever we change the INLINEP state (i.e.
722 ;;; an inline proclamation) we copy the structure so that former
723 ;;; INLINEP values are preserved.
724 (def!struct (defined-fun (:include global-var
725 (where-from :defined)
726 (kind :global-function)))
727 ;; The values of INLINEP and INLINE-EXPANSION initialized from the
728 ;; global environment.
729 (inlinep nil :type inlinep)
730 (inline-expansion nil :type (or cons null))
731 ;; the block-local definition of this function (either because it
732 ;; was semi-inline, or because it was defined in this block). If
733 ;; this function is not an entry point, then this may be deleted or
734 ;; LET-converted. Null if we haven't converted the expansion yet.
735 (functional nil :type (or functional null)))
736 (defprinter (defined-fun :identity t)
739 (functional :test functional))
743 ;;; We default the WHERE-FROM and TYPE slots to :DEFINED and FUNCTION.
744 ;;; We don't normally manipulate function types for defined functions,
745 ;;; but if someone wants to know, an approximation is there.
746 (def!struct (functional (:include leaf
747 (%source-name '.anonymous.)
748 (where-from :defined)
749 (type (specifier-type 'function))))
750 ;; (For public access to this slot, use LEAF-DEBUG-NAME.)
752 ;; the name of FUNCTIONAL for debugging purposes, or NIL if we
753 ;; should just let the SOURCE-NAME fall through
755 ;; Unlike the SOURCE-NAME slot, this slot's value should never
756 ;; affect ordinary code behavior, only debugging/diagnostic behavior.
758 ;; The value of this slot can be anything, except that it shouldn't
759 ;; be a legal function name, since otherwise debugging gets
760 ;; confusing. (If a legal function name is a good name for the
761 ;; function, it should be in %SOURCE-NAME, and then we shouldn't
762 ;; need a %DEBUG-NAME.) In SBCL as of 0.pre7.87, it's always a
763 ;; string unless it's NIL, since that's how CMU CL represented debug
764 ;; names. However, eventually I (WHN) think it we should start using
765 ;; list values instead, since they have much nicer print properties
766 ;; (abbreviation, skipping package prefixes when unneeded, and
767 ;; renaming package prefixes when we do things like renaming SB!EXT
770 ;; E.g. for the function which implements (DEFUN FOO ...), we could
774 ;; for the function which implements the top level form
775 ;; (IN-PACKAGE :FOO) we could have
777 ;; %DEBUG-NAME="top level form (IN-PACKAGE :FOO)"
778 ;; for the function which implements FOO in
779 ;; (DEFUN BAR (...) (FLET ((FOO (...) ...)) ...))
782 ;; %DEBUG-NAME="FLET FOO in BAR"
783 ;; and for the function which implements FOO in
784 ;; (DEFMACRO FOO (...) ...)
786 ;; %SOURCE-NAME=FOO (or maybe .ANONYMOUS.?)
787 ;; %DEBUG-NAME="DEFMACRO FOO"
789 :type (or null (not (satisfies legal-fun-name-p)))
791 ;; some information about how this function is used. These values
795 ;; an ordinary function, callable using local call
798 ;; a lambda that is used in only one local call, and has in
799 ;; effect been substituted directly inline. The return node is
800 ;; deleted, and the result is computed with the actual result
801 ;; continuation for the call.
804 ;; Similar to :LET, but the call is an MV-CALL.
807 ;; similar to a LET, but can have other than one call as long as
808 ;; there is at most one non-tail call.
811 ;; a lambda that is an entry-point for an optional-dispatch.
812 ;; Similar to NIL, but requires greater caution, since local call
813 ;; analysis may create new references to this function. Also, the
814 ;; function cannot be deleted even if it has *no* references. The
815 ;; OPTIONAL-DISPATCH is in the LAMDBA-OPTIONAL-DISPATCH.
818 ;; an external entry point lambda. The function it is an entry
819 ;; for is in the ENTRY-FUN slot.
822 ;; a top level lambda, holding a compiled top level form.
823 ;; Compiled very much like NIL, but provides an indication of
824 ;; top level context. A :TOPLEVEL lambda should have *no*
825 ;; references. Its ENTRY-FUN is a self-pointer.
828 ;; After a component is compiled, we clobber any top level code
829 ;; references to its non-closure XEPs with dummy FUNCTIONAL
830 ;; structures having this kind. This prevents the retained
831 ;; top level code from holding onto the IR for the code it
836 ;; special functions used internally by CATCH and UNWIND-PROTECT.
837 ;; These are pretty much like a normal function (NIL), but are
838 ;; treated specially by local call analysis and stuff. Neither
839 ;; kind should ever be given an XEP even though they appear as
840 ;; args to funny functions. An :ESCAPE function is never actually
841 ;; called, and thus doesn't need to have code generated for it.
844 ;; This function has been found to be uncallable, and has been
845 ;; marked for deletion.
846 (kind nil :type (member nil :optional :deleted :external :toplevel
847 :escape :cleanup :let :mv-let :assignment
849 ;; Is this a function that some external entity (e.g. the fasl dumper)
850 ;; refers to, so that even when it appears to have no references, it
851 ;; shouldn't be deleted? In the old days (before
852 ;; sbcl-0.pre7.37.flaky5.2) this was sort of implicitly true when
853 ;; KIND was :TOPLEVEL. Now it must be set explicitly, both for
854 ;; :TOPLEVEL functions and for any other kind of functions that we
855 ;; want to dump or return from #'CL:COMPILE or whatever.
856 (has-external-references-p nil)
857 ;; In a normal function, this is the external entry point (XEP)
858 ;; lambda for this function, if any. Each function that is used
859 ;; other than in a local call has an XEP, and all of the
860 ;; non-local-call references are replaced with references to the
863 ;; In an XEP lambda (indicated by the :EXTERNAL kind), this is the
864 ;; function that the XEP is an entry-point for. The body contains
865 ;; local calls to all the actual entry points in the function. In a
866 ;; :TOPLEVEL lambda (which is its own XEP) this is a self-pointer.
868 ;; With all other kinds, this is null.
869 (entry-fun nil :type (or functional null))
870 ;; the value of any inline/notinline declaration for a local function
871 (inlinep nil :type inlinep)
872 ;; If we have a lambda that can be used as in inline expansion for
873 ;; this function, then this is it. If there is no source-level
874 ;; lambda corresponding to this function then this is Null (but then
875 ;; INLINEP will always be NIL as well.)
876 (inline-expansion nil :type list)
877 ;; the lexical environment that the inline-expansion should be converted in
878 (lexenv *lexenv* :type lexenv)
879 ;; the original function or macro lambda list, or :UNSPECIFIED if
880 ;; this is a compiler created function
881 (arg-documentation nil :type (or list (member :unspecified)))
882 ;; various rare miscellaneous info that drives code generation & stuff
883 (plist () :type list))
884 (defprinter (functional :identity t)
888 ;;; FUNCTIONAL name operations
889 (defun functional-debug-name (functional)
890 ;; FUNCTIONAL-%DEBUG-NAME takes precedence over FUNCTIONAL-SOURCE-NAME
891 ;; here because we want different debug names for the functions in
892 ;; DEFUN FOO and FLET FOO even though they have the same source name.
893 (or (functional-%debug-name functional)
894 ;; Note that this will cause an error if the function is
895 ;; anonymous. In SBCL (as opposed to CMU CL) we make all
896 ;; FUNCTIONALs have debug names. The CMU CL code didn't bother
897 ;; in many FUNCTIONALs, especially those which were likely to be
898 ;; optimized away before the user saw them. However, getting
899 ;; that right requires a global understanding of the code,
900 ;; which seems bad, so we just require names for everything.
901 (leaf-source-name functional)))
903 ;;; The CLAMBDA only deals with required lexical arguments. Special,
904 ;;; optional, keyword and rest arguments are handled by transforming
905 ;;; into simpler stuff.
906 (def!struct (clambda (:include functional)
908 (:predicate lambda-p)
909 (:constructor make-lambda)
910 (:copier copy-lambda))
911 ;; list of LAMBDA-VAR descriptors for arguments
912 (vars nil :type list :read-only t)
913 ;; If this function was ever a :OPTIONAL function (an entry-point
914 ;; for an OPTIONAL-DISPATCH), then this is that OPTIONAL-DISPATCH.
915 ;; The optional dispatch will be :DELETED if this function is no
917 (optional-dispatch nil :type (or optional-dispatch null))
918 ;; the BIND node for this LAMBDA. This node marks the beginning of
919 ;; the lambda, and serves to explicitly represent the lambda binding
920 ;; semantics within the flow graph representation. This is null in
921 ;; deleted functions, and also in LETs where we deleted the call and
922 ;; bind (because there are no variables left), but have not yet
923 ;; actually deleted the LAMBDA yet.
924 (bind nil :type (or bind null))
925 ;; the RETURN node for this LAMBDA, or NIL if it has been deleted.
926 ;; This marks the end of the lambda, receiving the result of the
927 ;; body. In a LET, the return node is deleted, and the body delivers
928 ;; the value to the actual continuation. The return may also be
929 ;; deleted if it is unreachable.
930 (return nil :type (or creturn null))
931 ;; If this CLAMBDA is a LET, then this slot holds the LAMBDA whose
932 ;; LETS list we are in, otherwise it is a self-pointer.
933 (home nil :type (or clambda null))
934 ;; all the lambdas that have been LET-substituted in this lambda.
935 ;; This is only non-null in lambdas that aren't LETs.
936 (lets nil :type list)
937 ;; all the ENTRY nodes in this function and its LETs, or null in a LET
938 (entries nil :type list)
939 ;; CLAMBDAs which are locally called by this lambda, and other
940 ;; objects (closed-over LAMBDA-VARs and XEPs) which this lambda
941 ;; depends on in such a way that DFO shouldn't put them in separate
943 (calls-or-closes nil :type list)
944 ;; the TAIL-SET that this LAMBDA is in. This is null during creation.
946 ;; In CMU CL, and old SBCL, this was also NILed out when LET
947 ;; conversion happened. That caused some problems, so as of
948 ;; sbcl-0.pre7.37.flaky5.2 when I was trying to get the compiler to
949 ;; emit :EXTERNAL functions directly, and so now the value
950 ;; is no longer NILed out in LET conversion, but instead copied
951 ;; (so that any further optimizations on the rest of the tail
952 ;; set won't modify the value) if necessary.
953 (tail-set nil :type (or tail-set null))
954 ;; the structure which represents the phsical environment that this
955 ;; function's variables are allocated in. This is filled in by
956 ;; physical environment analysis. In a LET, this is EQ to our home's
957 ;; physical environment.
958 (physenv nil :type (or physenv null))
959 ;; In a LET, this is the NODE-LEXENV of the combination node. We
960 ;; retain it so that if the LET is deleted (due to a lack of vars),
961 ;; we will still have caller's lexenv to figure out which cleanup is
963 (call-lexenv nil :type (or lexenv null)))
964 (defprinter (clambda :conc-name lambda- :identity t)
967 (type :test (not (eq type *universal-type*)))
968 (where-from :test (not (eq where-from :assumed)))
969 (vars :prin1 (mapcar #'leaf-source-name vars)))
971 ;;; The OPTIONAL-DISPATCH leaf is used to represent hairy lambdas. It
972 ;;; is a FUNCTIONAL, like LAMBDA. Each legal number of arguments has a
973 ;;; function which is called when that number of arguments is passed.
974 ;;; The function is called with all the arguments actually passed. If
975 ;;; additional arguments are legal, then the LEXPR style MORE-ENTRY
976 ;;; handles them. The value returned by the function is the value
977 ;;; which results from calling the OPTIONAL-DISPATCH.
979 ;;; The theory is that each entry-point function calls the next entry
980 ;;; point tail-recursively, passing all the arguments passed in and
981 ;;; the default for the argument the entry point is for. The last
982 ;;; entry point calls the real body of the function. In the presence
983 ;;; of SUPPLIED-P args and other hair, things are more complicated. In
984 ;;; general, there is a distinct internal function that takes the
985 ;;; SUPPLIED-P args as parameters. The preceding entry point calls
986 ;;; this function with NIL filled in for the SUPPLIED-P args, while
987 ;;; the current entry point calls it with T in the SUPPLIED-P
990 ;;; Note that it is easy to turn a call with a known number of
991 ;;; arguments into a direct call to the appropriate entry-point
992 ;;; function, so functions that are compiled together can avoid doing
994 (def!struct (optional-dispatch (:include functional))
995 ;; the original parsed argument list, for anyone who cares
996 (arglist nil :type list)
997 ;; true if &ALLOW-OTHER-KEYS was supplied
998 (allowp nil :type boolean)
999 ;; true if &KEY was specified (which doesn't necessarily mean that
1000 ;; there are any &KEY arguments..)
1001 (keyp nil :type boolean)
1002 ;; the number of required arguments. This is the smallest legal
1003 ;; number of arguments.
1004 (min-args 0 :type unsigned-byte)
1005 ;; the total number of required and optional arguments. Args at
1006 ;; positions >= to this are &REST, &KEY or illegal args.
1007 (max-args 0 :type unsigned-byte)
1008 ;; list of the LAMBDAs which are the entry points for non-rest,
1009 ;; non-key calls. The entry for MIN-ARGS is first, MIN-ARGS+1
1010 ;; second, ... MAX-ARGS last. The last entry-point always calls the
1011 ;; main entry; in simple cases it may be the main entry.
1012 (entry-points nil :type list)
1013 ;; an entry point which takes MAX-ARGS fixed arguments followed by
1014 ;; an argument context pointer and an argument count. This entry
1015 ;; point deals with listifying rest args and parsing keywords. This
1016 ;; is null when extra arguments aren't legal.
1017 (more-entry nil :type (or clambda null))
1018 ;; the main entry-point into the function, which takes all arguments
1019 ;; including keywords as fixed arguments. The format of the
1020 ;; arguments must be determined by examining the arglist. This may
1021 ;; be used by callers that supply at least MAX-ARGS arguments and
1022 ;; know what they are doing.
1023 (main-entry nil :type (or clambda null)))
1024 (defprinter (optional-dispatch :identity t)
1027 (type :test (not (eq type *universal-type*)))
1028 (where-from :test (not (eq where-from :assumed)))
1034 (entry-points :test entry-points)
1035 (more-entry :test more-entry)
1038 ;;; The ARG-INFO structure allows us to tack various information onto
1039 ;;; LAMBDA-VARs during IR1 conversion. If we use one of these things,
1040 ;;; then the var will have to be massaged a bit before it is simple
1042 (def!struct arg-info
1043 ;; true if this arg is to be specially bound
1044 (specialp nil :type boolean)
1045 ;; the kind of argument being described. Required args only have arg
1046 ;; info structures if they are special.
1048 :type (member :required :optional :keyword :rest
1049 :more-context :more-count))
1050 ;; If true, this is the VAR for SUPPLIED-P variable of a keyword or
1051 ;; optional arg. This is true for keywords with non-constant
1052 ;; defaults even when there is no user-specified supplied-p var.
1053 (supplied-p nil :type (or lambda-var null))
1054 ;; the default for a keyword or optional, represented as the
1055 ;; original Lisp code. This is set to NIL in &KEY arguments that are
1056 ;; defaulted using the SUPPLIED-P arg.
1057 (default nil :type t)
1058 ;; the actual key for a &KEY argument. Note that in ANSI CL this is
1059 ;; not necessarily a keyword: (DEFUN FOO (&KEY ((BAR BAR))) ...).
1060 (key nil :type symbol))
1061 (defprinter (arg-info :identity t)
1062 (specialp :test specialp)
1064 (supplied-p :test supplied-p)
1065 (default :test default)
1068 ;;; The LAMBDA-VAR structure represents a lexical lambda variable.
1069 ;;; This structure is also used during IR1 conversion to describe
1070 ;;; lambda arguments which may ultimately turn out not to be simple
1073 ;;; LAMBDA-VARs with no REFs are considered to be deleted; physical
1074 ;;; environment analysis isn't done on these variables, so the back
1075 ;;; end must check for and ignore unreferenced variables. Note that a
1076 ;;; deleted LAMBDA-VAR may have sets; in this case the back end is
1077 ;;; still responsible for propagating the SET-VALUE to the set's CONT.
1078 (def!struct (lambda-var (:include basic-var))
1079 ;; true if this variable has been declared IGNORE
1080 (ignorep nil :type boolean)
1081 ;; the CLAMBDA that this var belongs to. This may be null when we are
1082 ;; building a lambda during IR1 conversion.
1083 (home nil :type (or null clambda))
1084 ;; This is set by physical environment analysis if it chooses an
1085 ;; indirect (value cell) representation for this variable because it
1086 ;; is both set and closed over.
1087 (indirect nil :type boolean)
1088 ;; The following two slots are only meaningful during IR1 conversion
1089 ;; of hairy lambda vars:
1091 ;; The ARG-INFO structure which holds information obtained from
1092 ;; &keyword parsing.
1093 (arg-info nil :type (or arg-info null))
1094 ;; if true, the GLOBAL-VAR structure for the special variable which
1095 ;; is to be bound to the value of this argument
1096 (specvar nil :type (or global-var null))
1097 ;; Set of the CONSTRAINTs on this variable. Used by constraint
1098 ;; propagation. This is left null by the lambda pre-pass if it
1099 ;; determine that this is a set closure variable, and is thus not a
1100 ;; good subject for flow analysis.
1101 (constraints nil :type (or sset null)))
1102 (defprinter (lambda-var :identity t)
1104 (type :test (not (eq type *universal-type*)))
1105 (where-from :test (not (eq where-from :assumed)))
1106 (ignorep :test ignorep)
1107 (arg-info :test arg-info)
1108 (specvar :test specvar))
1110 ;;;; basic node types
1112 ;;; A REF represents a reference to a LEAF. REF-REOPTIMIZE is
1113 ;;; initially (and forever) NIL, since REFs don't receive any values
1114 ;;; and don't have any IR1 optimizer.
1115 (defstruct (ref (:include node (:reoptimize nil))
1116 (:constructor make-ref (derived-type leaf))
1118 ;; The leaf referenced.
1119 (leaf nil :type leaf))
1120 (defprinter (ref :identity t)
1123 ;;; Naturally, the IF node always appears at the end of a block.
1124 ;;; NODE-CONT is a dummy continuation, and is there only to keep
1126 (defstruct (cif (:include node)
1129 (:constructor make-if)
1131 ;; CONTINUATION for the predicate
1132 (test (missing-arg) :type continuation)
1133 ;; the blocks that we execute next in true and false case,
1134 ;; respectively (may be the same)
1135 (consequent (missing-arg) :type cblock)
1136 (alternative (missing-arg) :type cblock))
1137 (defprinter (cif :conc-name if- :identity t)
1138 (test :prin1 (continuation-use test))
1142 (defstruct (cset (:include node
1143 (derived-type *universal-type*))
1146 (:constructor make-set)
1148 ;; descriptor for the variable set
1149 (var (missing-arg) :type basic-var)
1150 ;; continuation for the value form
1151 (value (missing-arg) :type continuation))
1152 (defprinter (cset :conc-name set- :identity t)
1154 (value :prin1 (continuation-use value)))
1156 ;;; The BASIC-COMBINATION structure is used to represent both normal
1157 ;;; and multiple value combinations. In a local function call, this
1158 ;;; node appears at the end of its block and the body of the called
1159 ;;; function appears as the successor. The NODE-CONT remains the
1160 ;;; continuation which receives the value of the call.
1161 (defstruct (basic-combination (:include node)
1164 ;; continuation for the function
1165 (fun (missing-arg) :type continuation)
1166 ;; list of CONTINUATIONs for the args. In a local call, an argument
1167 ;; continuation may be replaced with NIL to indicate that the
1168 ;; corresponding variable is unreferenced, and thus no argument
1169 ;; value need be passed.
1170 (args nil :type list)
1171 ;; the kind of function call being made. :LOCAL means that this is a
1172 ;; local call to a function in the same component, and that argument
1173 ;; syntax checking has been done, etc. Calls to known global
1174 ;; functions are represented by storing the FUNCTION-INFO for the
1175 ;; function in this slot. :FULL is a call to an (as yet) unknown
1176 ;; function. :ERROR is like :FULL, but means that we have discovered
1177 ;; that the call contains an error, and should not be reconsidered
1178 ;; for optimization.
1179 (kind :full :type (or (member :local :full :error) function-info))
1180 ;; some kind of information attached to this node by the back end
1183 ;;; The COMBINATION node represents all normal function calls,
1184 ;;; including FUNCALL. This is distinct from BASIC-COMBINATION so that
1185 ;;; an MV-COMBINATION isn't COMBINATION-P.
1186 (defstruct (combination (:include basic-combination)
1187 (:constructor make-combination (fun))
1189 (defprinter (combination :identity t)
1190 (fun :prin1 (continuation-use fun))
1191 (args :prin1 (mapcar (lambda (x)
1193 (continuation-use x)
1197 ;;; An MV-COMBINATION is to MULTIPLE-VALUE-CALL as a COMBINATION is to
1198 ;;; FUNCALL. This is used to implement all the multiple-value
1199 ;;; receiving forms.
1200 (defstruct (mv-combination (:include basic-combination)
1201 (:constructor make-mv-combination (fun))
1203 (defprinter (mv-combination)
1204 (fun :prin1 (continuation-use fun))
1205 (args :prin1 (mapcar #'continuation-use args)))
1207 ;;; The BIND node marks the beginning of a lambda body and represents
1208 ;;; the creation and initialization of the variables.
1209 (defstruct (bind (:include node)
1211 ;; the lambda we are binding variables for. Null when we are
1212 ;; creating the LAMBDA during IR1 translation.
1213 (lambda nil :type (or clambda null)))
1217 ;;; The RETURN node marks the end of a lambda body. It collects the
1218 ;;; return values and represents the control transfer on return. This
1219 ;;; is also where we stick information used for TAIL-SET type
1221 (defstruct (creturn (:include node)
1222 (:conc-name return-)
1223 (:predicate return-p)
1224 (:constructor make-return)
1225 (:copier copy-return))
1226 ;; the lambda we are returning from. Null temporarily during
1228 (lambda nil :type (or clambda null))
1229 ;; the continuation which yields the value of the lambda
1230 (result (missing-arg) :type continuation)
1231 ;; the union of the node-derived-type of all uses of the result
1232 ;; other than by a local call, intersected with the result's
1233 ;; asserted-type. If there are no non-call uses, this is
1235 (result-type *wild-type* :type ctype))
1236 (defprinter (creturn :conc-name return- :identity t)
1240 ;;;; non-local exit support
1242 ;;;; In IR1, we insert special nodes to mark potentially non-local
1245 ;;; The ENTRY node serves to mark the start of the dynamic extent of a
1246 ;;; lexical exit. It is the mess-up node for the corresponding :Entry
1248 (defstruct (entry (:include node)
1250 ;; All of the Exit nodes for potential non-local exits to this point.
1251 (exits nil :type list)
1252 ;; The cleanup for this entry. NULL only temporarily.
1253 (cleanup nil :type (or cleanup null)))
1254 (defprinter (entry :identity t))
1256 ;;; The EXIT node marks the place at which exit code would be emitted,
1257 ;;; if necessary. This is interposed between the uses of the exit
1258 ;;; continuation and the exit continuation's DEST. Instead of using
1259 ;;; the returned value being delivered directly to the exit
1260 ;;; continuation, it is delivered to our VALUE continuation. The
1261 ;;; original exit continuation is the exit node's CONT.
1262 (defstruct (exit (:include node)
1264 ;; the ENTRY node that this is an exit for. If null, this is a
1265 ;; degenerate exit. A degenerate exit is used to "fill" an empty
1266 ;; block (which isn't allowed in IR1.) In a degenerate exit, Value
1267 ;; is always also null.
1268 (entry nil :type (or entry null))
1269 ;; the continuation yielding the value we are to exit with. If NIL,
1270 ;; then no value is desired (as in GO).
1271 (value nil :type (or continuation null)))
1272 (defprinter (exit :identity t)
1274 (value :test value))
1276 ;;;; miscellaneous IR1 structures
1278 (defstruct (undefined-warning
1279 #-no-ansi-print-object
1280 (:print-object (lambda (x s)
1281 (print-unreadable-object (x s :type t)
1282 (prin1 (undefined-warning-name x) s))))
1284 ;; the name of the unknown thing
1285 (name nil :type (or symbol list))
1286 ;; the kind of reference to NAME
1287 (kind (missing-arg) :type (member :function :type :variable))
1288 ;; the number of times this thing was used
1289 (count 0 :type unsigned-byte)
1290 ;; a list of COMPILER-ERROR-CONTEXT structures describing places
1291 ;; where this thing was used. Note that we only record the first
1292 ;; *UNDEFINED-WARNING-LIMIT* calls.
1293 (warnings () :type list))
1295 ;;; a helper for the POLICY macro, defined late here so that the
1296 ;;; various type tests can be inlined
1297 (declaim (ftype (function ((or list lexenv node functional)) list)
1299 (defun %coerce-to-policy (thing)
1300 (let ((result (etypecase thing
1302 (lexenv (lexenv-policy thing))
1303 (node (lexenv-policy (node-lexenv thing)))
1304 (functional (lexenv-policy (functional-lexenv thing))))))
1305 ;; Test the first element of the list as a rudimentary sanity
1306 ;; that it really does look like a valid policy.
1307 (aver (or (null result) (policy-quality-name-p (caar result))))
1311 ;;;; Freeze some structure types to speed type testing.
1314 (declaim (freeze-type node leaf lexenv continuation cblock component cleanup
1315 physenv tail-set nlx-info))