| blob | 8e4e15488f1e8111ae6246a453367b5e6fd75977 |
1 ;;;; the top level interfaces to the compiler, plus some other
2 ;;;; compiler-related stuff (e.g. CL:CALL-ARGUMENTS-LIMIT) which
3 ;;;; doesn't obviously belong anywhere else
5 ;;;; This software is part of the SBCL system. See the README file for
6 ;;;; more information.
7 ;;;;
8 ;;;; This software is derived from the CMU CL system, which was
9 ;;;; written at Carnegie Mellon University and released into the
10 ;;;; public domain. The software is in the public domain and is
11 ;;;; provided with absolutely no warranty. See the COPYING and CREDITS
12 ;;;; files for more information.
16 ;;; FIXME: Doesn't this belong somewhere else, like early-c.lisp?
35 ;;; Whether call of a function which cannot be defined causes a full
36 ;;; warning.
42 ;;; Set to NIL to disable loop analysis for register allocation.
45 ;;; Bind this to a stream to capture various internal debugging output.
48 ;;; The current block compilation state. These are initialized to the
49 ;;; :BLOCK-COMPILE and :ENTRY-POINTS arguments that COMPILE-FILE was
50 ;;; called with.
51 ;;;
52 ;;; *BLOCK-COMPILE-ARG* holds the original value of the :BLOCK-COMPILE
53 ;;; argument, which overrides any internal declarations.
60 ;;; When block compiling, used by PROCESS-FORM to accumulate top level
61 ;;; lambdas resulting from compiling subforms. (In reverse order.)
65 ;;; The current non-macroexpanded toplevel form as printed when
66 ;;; *compile-print* is true.
70 #!+sb-doc
73 #!+sb-doc
76 #!+sb-doc
77 "When this is true, the compiler prints to *STANDARD-OUTPUT* progress
78 information about the phases of compilation of each function. (This
82 #!+sb-doc
83 "The defaulted pathname of the file currently being compiled, or NIL if not
86 #!+sb-doc
87 "The TRUENAME of the file currently being compiled, or NIL if not
94 ;;; the SOURCE-INFO structure for the current compilation. This is
95 ;;; null globally to indicate that we aren't currently in any
96 ;;; identifiable compilation.
99 ;;; This is true if we are within a WITH-COMPILATION-UNIT form (which
100 ;;; normally causes nested uses to be no-ops).
103 ;;; Count of the number of compilation units dynamically enclosed by
104 ;;; the current active WITH-COMPILATION-UNIT that were unwound out of.
107 ;;; Mumble conditional on *COMPILE-PROGRESS*.
120 \f
121 ;;;; WITH-COMPILATION-UNIT and WITH-COMPILATION-VALUES
124 #!+sb-doc
125 "WITH-COMPILATION-UNIT ({Key Value}*) Form*
126 This form affects compilations that take place within its dynamic extent. It
127 is intended to be wrapped around the compilation of all files in the same
128 system. These keywords are defined:
130 :OVERRIDE Boolean-Form
131 One of the effects of this form is to delay undefined warnings
132 until the end of the form, instead of giving them at the end of each
133 compilation. If OVERRIDE is NIL (the default), then the outermost
134 WITH-COMPILATION-UNIT form grabs the undefined warnings. Specifying
135 OVERRIDE true causes that form to grab any enclosed warnings, even if
136 it is enclosed by another WITH-COMPILATION-UNIT.
138 :SOURCE-PLIST Plist-Form
139 Attaches the value returned by the Plist-Form to internal debug-source
140 information of functions compiled in within the dynamic contour.
141 Primarily for use by development environments, in order to eg. associate
142 function definitions with editor-buffers. Can be accessed as
143 SB-INTROSPECT:DEFINITION-SOURCE-PLIST. If multiple, nested
144 WITH-COMPILATION-UNITs provide :SOURCE-PLISTs, they are appended
145 togather, innermost left. If Unaffected by :OVERRIDE."
155 ;; Inside another WITH-COMPILATION-UNIT, a WITH-COMPILATION-UNIT is
156 ;; ordinarily (unless OVERRIDE) basically a no-op.
180 ;;; Is FUN-NAME something that no conforming program can rely on
181 ;;; defining as a function?
186 ;;; This is to be called at the end of a compilation unit. It signals
187 ;;; any residual warnings about unknown stuff, then prints the total
188 ;;; error counts. ABORT-P should be true when the compilation unit was
189 ;;; aborted by throwing out. ABORT-COUNT is the number of dynamically
190 ;;; enclosed nested compilation units that were aborted.
211 #+sb-xc-host nil
215 "~@<There is no function named ~S. References to ~S in ~
216 some contexts (like starts of blocks) have special ~
217 meaning, but here it would have to be a function, ~
218 and that shouldn't be right.~:@>"
219 name name))
222 "~@<The ~(~A~) ~S is undefined, and its name is ~
223 reserved by ANSI CL so that even if it were ~
224 defined later, the code doing so would not be ~
225 portable.~:@>"
226 kind name)))
235 "~W more use~:P of undefined ~(~A~) ~S"
236 more kind name)
238 "~W more use~:P of undefined ~(~A~) ~S"
239 more kind name)))))))
248 "~:[This ~(~A~) is~;These ~(~A~)s are~] undefined:~
249 ~% ~{~<~% ~1:;~S~>~^ ~}"
252 "~:[This ~(~A~) is~;These ~(~A~)s are~] undefined:~
253 ~% ~{~<~% ~1:;~S~>~^ ~}"
264 ~[~:;~:*~& caught ~W fatal ERROR condition~:P~]~
265 ~[~:;~:*~& caught ~W ERROR condition~:P~]~
266 ~[~:;~:*~& caught ~W WARNING condition~:P~]~
267 ~[~:;~:*~& caught ~W STYLE-WARNING condition~:P~]~
268 ~[~:;~:*~& printed ~W note~:P~]"
269 abort-p
278 ;;; Evaluate BODY, then return (VALUES BODY-VALUE WARNINGS-P
279 ;;; FAILURE-P), where BODY-VALUE is the first value of the body, and
280 ;;; WARNINGS-P and FAILURE-P are as in CL:COMPILE or CL:COMPILE-FILE.
281 ;;; This also wraps up WITH-IR1-NAMESPACE functionality.
289 \f
290 ;;;; component compilation
293 #!+sb-doc
294 "The upper limit on the number of times that we will consecutively do IR1
295 optimization that doesn't introduce any new code. A finite limit is
301 ;;; Repeatedly optimize COMPONENT until no further optimizations can
302 ;;; be found or we hit our iteration limit. When we hit the limit, we
303 ;;; clear the component and block REOPTIMIZE flags to discourage the
304 ;;; next optimization attempt from pounding on the same code.
348 ;;; KLUDGE: This was bumped from 5 to 10 in a DTC patch ported by MNA
349 ;;; from CMU CL into sbcl-0.6.11.44, the same one which allowed IR1
350 ;;; transforms to be delayed. Either DTC or MNA or both didn't explain
351 ;;; why, and I don't know what the rationale was. -- WHN 2001-04-28
352 ;;;
353 ;;; FIXME: It would be good to document why it's important to have a
354 ;;; large value here, and what the drawbacks of an excessively large
355 ;;; value are; and it might also be good to make it depend on
356 ;;; optimization policy.
362 ;;; Iterate doing FIND-DFO until no new dead code is discovered.
375 ;;; Do all the IR1 phases for a non-top-level component.
401 ;; We delay the generation of type checks until
402 ;; the type constraints have had time to
403 ;; propagate, else the compiler can confuse itself.
433 ;; Assign BLOCK-NUMBER for any cleanup blocks introduced by
434 ;; stack analysis. There shouldn't be any unreachable code after
435 ;; control, so this won't delete anything.
483 #-sb-xc-host
495 code-length
496 trace-table
497 fixup-notes
503 code-length
504 trace-table
505 fixup-notes
509 ;; We're done, so don't bother keeping anything around.
514 ;;; Delete components with no external entry points before we try to
515 ;;; generate code. Unreachable closures can cause IR2 conversion to
516 ;;; puke on itself, since it is the reference to the closure which
517 ;;; normally causes the components to be combined.
524 (:external
532 ;; miscellaneous sanity checks
533 ;;
534 ;; FIXME: These are basically pretty wimpy compared to the checks done
535 ;; by the old CHECK-IR1-CONSISTENCY code. It would be really nice to
536 ;; make those internal consistency checks work again and use them.
541 ;; sanity check to prevent weirdness from propagating insidiously as
542 ;; far from its root cause as it did in bug 138: Make sure that
543 ;; thing-to-COMPONENT links are consistent.
556 #|
568 |#
570 ;; FIXME: What is MAYBE-MUMBLE for? Do we need it any more?
584 \f
585 ;;;; clearing global data structures
586 ;;;;
587 ;;;; FIXME: Is it possible to get rid of this stuff, getting rid of
588 ;;;; global data structures entirely when possible and consing up the
589 ;;;; others from scratch instead of clearing and reusing them?
591 ;;; Clear the INFO in constants in the *FREE-VARS*, etc. In
592 ;;; addition to allowing stuff to be reclaimed, this is required for
593 ;;; correct assignment of constant offsets, since we need to assign a
594 ;;; new offset for each component. We don't clear the FUNCTIONAL-INFO
595 ;;; slots, since they are used to keep track of functions across
596 ;;; component boundaries.
609 ;;; Blow away the REFS for all global variables, and let COMPONENT
610 ;;; be recycled.
622 x))
630 ;;; Clear global variables used by the compiler.
631 ;;;
632 ;;; FIXME: It seems kinda nasty and unmaintainable to have to do this,
633 ;;; and it adds overhead even when people aren't using the compiler.
634 ;;; Perhaps we could make these global vars unbound except when
635 ;;; actually in use, so that this function could go away.
638 ;; Clear global tables.
644 ;; Clear debug counters and tables.
660 ;; (Note: The CMU CL code used to set CL::*GENSYM-COUNTER* to zero here.
661 ;; Superficially, this seemed harmful -- the user could reasonably be
662 ;; surprised if *GENSYM-COUNTER* turned back to zero when something was
663 ;; compiled. A closer inspection showed that this actually turned out to be
664 ;; harmless in practice, because CLEAR-STUFF was only called from within
665 ;; forms which bound CL::*GENSYM-COUNTER* to zero. However, this means that
666 ;; even though zeroing CL::*GENSYM-COUNTER* here turned out to be harmless in
667 ;; practice, it was also useless in practice. So we don't do it any more.)
670 \f
671 ;;;; trace output
673 ;;; Print out some useful info about COMPONENT to STREAM.
694 \f
695 ;;;; file reading
696 ;;;;
697 ;;;; When reading from a file, we have to keep track of some source
698 ;;;; information. We also exploit our ability to back up for printing
699 ;;;; the error context and for recovering from errors.
700 ;;;;
701 ;;;; The interface we provide to this stuff is the stream-oid
702 ;;;; SOURCE-INFO structure. The bookkeeping is done as a side effect
703 ;;;; of getting the next source form.
705 ;;; A FILE-INFO structure holds all the source information for a
706 ;;; given file.
708 ;; If a file, the truename of the corresponding source file. If from
709 ;; a Lisp form, :LISP. If from a stream, :STREAM.
711 ;; the external format that we'll call OPEN with, if NAME is a file.
713 ;; the defaulted, but not necessarily absolute file name (i.e. prior
714 ;; to TRUENAME call.) Null if not a file. This is used to set
715 ;; *COMPILE-FILE-PATHNAME*, and if absolute, is dumped in the
716 ;; debug-info.
718 ;; the file's write date (if relevant)
720 ;; the source path root number of the first form in this file (i.e.
721 ;; the total number of forms converted previously in this
722 ;; compilation)
724 ;; parallel vectors containing the forms read out of the file and
725 ;; the file positions that reading of each form started at (i.e. the
726 ;; end of the previous form)
730 ;;; The SOURCE-INFO structure provides a handle on all the source
731 ;;; information for an entire compilation.
733 #-no-ansi-print-object
737 ;; the UT that compilation started at
739 ;; the FILE-INFO structure for this compilation
741 ;; the stream that we are using to read the FILE-INFO, or NIL if
742 ;; no stream has been opened yet
745 ;;; Given a pathname, return a SOURCE-INFO structure.
749 :external-format external-format
754 ;;; Return a SOURCE-INFO to describe the incremental compilation of FORM.
761 ;;; Return a SOURCE-INFO which will read from STREAM.
767 ;;; Return a form read from STREAM; or for EOF use the trick,
768 ;;; popularized by Kent Pitman, of returning STREAM itself. If an
769 ;;; error happens, then convert it to standard abort-the-compilation
770 ;;; error condition (possibly recording some extra location
771 ;;; information).
776 :condition condition
777 ;; We don't need to supply :POSITION here because
778 ;; READER-ERRORs already know their position in the file.
779 ))
780 ;; ANSI, in its wisdom, says that READ should return END-OF-FILE
781 ;; (and that this is not a READER-ERROR) when it encounters end of
782 ;; file in the middle of something it's trying to read.
785 :condition condition
786 ;; We need to supply :POSITION here because the END-OF-FILE
787 ;; condition doesn't carry the position that the user
788 ;; probably cares about, where the failed READ began.
791 ;;; If STREAM is present, return it, otherwise open a stream to the
792 ;;; current file. There must be a current file.
793 ;;;
794 ;;; FIXME: This is probably an unnecessarily roundabout way to do
795 ;;; things now that we process a single file in COMPILE-FILE (unlike
796 ;;; the old CMU CL code, which accepted multiple files). Also, the old
797 ;;; comment said
798 ;;; When we open a new file, we also reset *PACKAGE* and policy.
799 ;;; This gives the effect of rebinding around each file.
800 ;;; which doesn't seem to be true now. Check to make sure that if
801 ;;; such rebinding is necessary, it's still done somewhere.
814 ;;; Close the stream in INFO if it is open.
822 ;;; Read and compile the source file.
839 nil)))))))
841 ;;; Return the INDEX'th source form read from INFO and the position
842 ;;; where it was read.
848 \f
849 ;;;; processing of top level forms
851 ;;; This is called by top level form processing when we are ready to
852 ;;; actually compile something. If *BLOCK-COMPILE* is T, then we still
853 ;;; convert the form, but delay compilation, pushing the result on
854 ;;; *TOPLEVEL-LAMBDAS* instead.
869 nil)))
871 ;;; Macroexpand FORM in the current environment with an error handler.
872 ;;; We only expand one level, so that we retain all the intervening
873 ;;; forms in the source path.
881 condition))))
883 ;;; Process a PROGN-like portion of a top level form. FORMS is a list of
884 ;;; the forms, and PATH is the source path of the FORM they came out of.
885 ;;; COMPILE-TIME-TOO is as in ANSI "3.2.3.1 Processing of Top Level Forms".
891 ;;; Process a top level use of LOCALLY, or anything else (e.g.
892 ;;; MACROLET) at top level which has declarations and ordinary forms.
893 ;;; We parse declarations and then recursively process the body.
899 ;; FIXME: VALUES declaration
900 ;;
901 ;; Binding *POLICY* is pretty much of a hack, since it
902 ;; causes LOCALLY to "capture" enclosed proclamations. It
903 ;; is necessary because CONVERT-AND-MAYBE-COMPILE uses the
904 ;; value of *POLICY* as the policy. The need for this hack
905 ;; is due to the quirk that there is no way to represent in
906 ;; a POLICY that an optimize quality came from the default.
907 ;;
908 ;; FIXME: Ideally, something should be done so that DECLAIM
909 ;; inside LOCALLY works OK. Failing that, at least we could
910 ;; issue a warning instead of silently screwing up.
912 ;; This is probably also a hack
914 ;; ditto
918 ;;; Parse an EVAL-WHEN situations list, returning three flags,
919 ;;; (VALUES COMPILE-TOPLEVEL LOAD-TOPLEVEL EXECUTE), indicating
920 ;;; the types of situations present in the list.
924 '(:compile-toplevel
925 compile
926 :load-toplevel
927 load
928 :execute
929 eval)))
934 deprecated-names)))
936 situations)
941 ;;; utilities for extracting COMPONENTs of FUNCTIONALs
952 result))))
956 result))))
959 &key
960 name
962 ;; I'd thought NIL should
963 ;; work, but it doesn't.
964 ;; -- WHN 2001-09-20
974 definition
984 fun)))
986 ;;; Compile LAMBDA-EXPRESSION into *COMPILE-OBJECT*, returning a
987 ;;; description of the result.
988 ;;; * If *COMPILE-OBJECT* is a CORE-OBJECT, then write the function
989 ;;; into core and return the compiled FUNCTION value.
990 ;;; * If *COMPILE-OBJECT* is a fasl file, then write the function
991 ;;; into the fasl file and return a dump handle.
992 ;;;
993 ;;; If NAME is provided, then we try to use it as the name of the
994 ;;; function for debugging/diagnostic information.
997 &key
998 name
1000 ;; This magical idiom seems to be the appropriate
1001 ;; path for compiling standalone LAMBDAs, judging
1002 ;; from the CMU CL code and experiment, so it's a
1003 ;; nice default for things where we don't have a
1004 ;; real source path (as in e.g. inside CL:COMPILE).
1013 :name name
1016 ;; FIXME: The compile-it code from here on is sort of a
1017 ;; twisted version of the code in COMPILE-TOPLEVEL. It'd be
1018 ;; better to find a way to share the code there; or
1019 ;; alternatively, to use this code to replace the code there.
1020 ;; (The second alternative might be pretty easy if we used
1021 ;; the :LOCALL-ONLY option to IR1-FOR-LAMBDA. Then maybe the
1022 ;; whole FUNCTIONAL-KIND=:TOPLEVEL case could go away..)
1044 result
1045 ;; KLUDGE: This code duplicates some other code in this
1046 ;; file. In the great reorganzation, the flow of program
1047 ;; logic changed from the original CMUCL model, and that
1048 ;; path (as of sbcl-0.7.5 in SUB-COMPILE-FILE) was no
1049 ;; longer followed for CORE-OBJECTS, leading to BUG
1050 ;; 156. This place is transparently not the right one for
1051 ;; this code, but I don't have a clear enough overview of
1052 ;; the compiler to know how to rearrange it all so that
1053 ;; this operation fits in nicely, and it was blocking
1054 ;; reimplementation of (DECLAIM (INLINE FOO)) (MACROLET
1055 ;; ((..)) (DEFUN FOO ...))
1056 ;;
1057 ;; FIXME: This KLUDGE doesn't solve all the problem in an
1058 ;; ideal way, as (1) definitions typed in at the REPL
1059 ;; without an INLINE declaration will give a NULL
1060 ;; FUNCTION-LAMBDA-EXPRESSION (allowable, but not ideal)
1061 ;; and (2) INLINE declarations will yield a
1062 ;; FUNCTION-LAMBDA-EXPRESSION headed by
1063 ;; SB-C:LAMBDA-WITH-LEXENV, even for null LEXENV. -- CSR,
1064 ;; 2002-07-02
1065 ;;
1066 ;; (2) is probably fairly easy to fix -- it is, after all,
1067 ;; a matter of list manipulation (or possibly of teaching
1068 ;; CL:FUNCTION about SB-C:LAMBDA-WITH-LEXENV). (1) is
1069 ;; significantly harder, as the association between
1070 ;; function object and source is a tricky one.
1071 ;;
1072 ;; FUNCTION-LAMBDA-EXPRESSION "works" (i.e. returns a
1073 ;; non-NULL list) when the function in question has been
1074 ;; compiled by (COMPILE <x> '(LAMBDA ...)); it does not
1075 ;; work when it has been compiled as part of the top-level
1076 ;; EVAL strategy of compiling everything inside (LAMBDA ()
1077 ;; ...). -- CSR, 2002-11-02
1089 (%compile lambda-expression
1091 :name name
1105 form)
1114 form)
1118 ;;; Process a top level FORM with the specified source PATH.
1119 ;;; * If this is a magic top level form, then do stuff.
1120 ;;; * If this is a macro, then expand it.
1121 ;;; * Otherwise, just compile it.
1122 ;;;
1123 ;;; COMPILE-TIME-TOO is as defined in ANSI
1124 ;;; "3.2.3.1 Processing of Top Level Forms".
1134 path)
1139 ;; When we're cross-compiling, consider: what should we
1140 ;; do when we hit e.g.
1141 ;; (EVAL-WHEN (:COMPILE-TOPLEVEL)
1142 ;; (DEFUN FOO (X) (+ 7 X)))?
1143 ;; DEFUN has a macro definition in the cross-compiler,
1144 ;; and a different macro definition in the target
1145 ;; compiler. The only sensible thing is to use the
1146 ;; target compiler's macro definition, since the
1147 ;; cross-compiler's macro is in general into target
1148 ;; functions which can't meaningfully be executed at
1149 ;; cross-compilation time. So make sure we do the EVAL
1150 ;; here, before we macroexpand.
1151 ;;
1152 ;; Then things get even dicier with something like
1153 ;; (DEFCONSTANT-EQX SB!XC:LAMBDA-LIST-KEYWORDS ..)
1154 ;; where we have to make sure that we don't uncross
1155 ;; the SB!XC: prefix before we do EVAL, because otherwise
1156 ;; we'd be trying to redefine the cross-compilation host's
1157 ;; constants.
1158 ;;
1159 ;; (Isn't it fun to cross-compile Common Lisp?:-)
1160 #+sb-xc-host
1165 ;; like SB!XC:DEFCONSTANT and SB!XC:DEFTYPE
1166 ;; should be equivalent to their CL: counterparts
1167 ;; when being compiled as target code. We leave
1168 ;; the rest of the form uncrossed because macros
1169 ;; might yet expand into EVAL-WHEN stuff, and
1170 ;; things inside EVAL-WHEN can't be uncrossed
1171 ;; until after we've EVALed them in the
1172 ;; cross-compilation host.)
1176 slightly-uncrossed)))
1178 ;; (Now that we're no longer processing toplevel
1179 ;; forms, and hence no longer need to worry about
1180 ;; EVAL-WHEN, we can uncross everything.)
1182 ;; (We have to demote COMPILE-TIME-TOO to NIL
1183 ;; here, no matter what it was before, since
1184 ;; otherwise we'd tend to EVAL subforms more than
1185 ;; once, because of WHEN COMPILE-TIME-TOO form
1186 ;; above.)
1188 ;; When we're not cross-compiling, we only need to
1189 ;; macroexpand once, so we can follow the 1-thru-6
1190 ;; sequence of steps in ANSI's "3.2.3.1 Processing of
1191 ;; Top Level Forms".
1192 #-sb-xc-host
1202 path
1203 compile-time-too)))))))
1205 #+sb-xc-host
1206 ;; (There are no xc EVAL-WHEN issues in the ATOM case until
1207 ;; (1) SBCL gets smart enough to handle global
1208 ;; DEFINE-SYMBOL-MACRO or SYMBOL-MACROLET and (2) SBCL
1209 ;; implementors start using symbol macros in a way which
1210 ;; interacts with SB-XC/CL distinction.)
1212 #-sb-xc-host
1218 form))))
1220 ;; In the cross-compiler, top level COLD-FSET arranges
1221 ;; for static linking at cold init time.
1222 #+sb-xc-host
1228 lambda-expression
1229 path)))
1235 ;; CT, LT, and E here are as in Figure 3-7 of ANSI
1236 ;; "3.2.3.1 Processing of Top Level Forms".
1241 e))))
1243 body path new-compile-time-too))
1249 magic
1254 path
1255 compile-time-too))
1259 magic
1263 path
1264 compile-time-too
1274 \f
1275 ;;;; load time value support
1276 ;;;;
1277 ;;;; (See EMIT-MAKE-LOAD-FORM.)
1279 ;;; Return T if we are currently producing a fasl file and hence
1280 ;;; constants need to be dumped carefully.
1284 ;;; Compile FORM and arrange for it to be called at load-time. Return
1285 ;;; the dumper handle and our best guess at the type of the object.
1295 ;;; Compile the FORMS and arrange for them to be called (for effect,
1296 ;;; not value) at load time.
1301 ;;; Do the actual work of COMPILE-LOAD-TIME-VALUE or
1302 ;;; COMPILE-MAKE-LOAD-FORM-INIT-FORMS.
1308 lambda)))
1310 ;;; This is called by COMPILE-TOPLEVEL when it was passed T for
1311 ;;; LOAD-TIME-VALUE-P (which happens in COMPILE-LOAD-TIME-STUFF). We
1312 ;;; don't try to combine this component with anything else and frob
1313 ;;; the name. If not in a :TOPLEVEL component, then don't bother
1314 ;;; compiling, because it was merged with a run-time component.
1323 \f
1324 ;;;; COMPILE-FILE
1334 ;;; Smash LAMBDAS into a single component, compile it, and arrange for
1335 ;;; the resulting function to be called.
1345 ;;; Compile top level code and call the top level lambdas. We pick off
1346 ;;; top level lambdas in non-top-level components here, calling
1347 ;;; SUB-c-t-l-l on each subsequence of normal top level lambdas.
1356 lambdas
1357 ;; this used to read ":start start", but
1358 ;; start can be greater than len, which
1359 ;; is an error according to ANSI - CSR,
1360 ;; 2002-04-25
1362 len)))
1371 ;;; Compile LAMBDAS (a list of CLAMBDAs for top level forms) into the
1372 ;;; object file.
1373 ;;;
1374 ;;; LOAD-TIME-VALUE-P seems to control whether it's MAKE-LOAD-FORM and
1375 ;;; COMPILE-LOAD-TIME-VALUE stuff. -- WHN 20000201
1409 ;;; Actually compile any stuff that has been queued up for block
1410 ;;; compilation.
1430 lexenv))
1434 nil
1450 lexenv))
1460 ;;; Read all forms from INFO and compile them, with output to OBJECT.
1461 ;;; Return (VALUES NIL WARNINGS-P FAILURE-P).
1488 ;; FIXME: Do we need this rebinding here? It's a literal
1489 ;; translation of the old CMU CL rebinding to
1490 ;; (OR *BACKEND-INFO-ENVIRONMENT* *INFO-ENVIRONMENT*),
1491 ;; and it's not obvious whether the rebinding to itself is
1492 ;; needed that SBCL doesn't need *BACKEND-INFO-ENVIRONMENT*.
1509 nil)))
1510 ;; Some errors are sufficiently bewildering that we just fail
1511 ;; immediately, without trying to recover and compile more of
1512 ;; the input file.
1517 "~@<compilation aborted because of fatal error: ~2I~_~A~:>"
1518 condition))
1521 ;;; Return a pathname for the named file. The file must exist.
1530 new
1543 ;;; Print some junk at the beginning and end of compilation.
1551 file-info)
1553 :print-weekday nil
1560 won
1566 ;;; Open some files and call SUB-COMPILE-FILE. If something unwinds
1567 ;;; out of the compile, then abort the writing of the output file, so
1568 ;;; that we don't overwrite it with known garbage.
1571 &key
1573 ;; ANSI options
1575 ;; FIXME: ANSI doesn't seem to say anything about
1576 ;; *COMPILE-VERBOSE* and *COMPILE-PRINT* being rebound by this
1577 ;; function..
1582 ;; extensions
1585 #!+sb-doc
1586 "Compile INPUT-FILE, producing a corresponding fasl file and
1587 returning its filename.
1589 :PRINT
1590 If true, a message per non-macroexpanded top level form is printed
1591 to *STANDARD-OUTPUT*. Top level forms that whose subforms are
1592 processed as top level forms (eg. EVAL-WHEN, MACROLET, PROGN) receive
1593 no such message, but their subforms do.
1595 As an extension to ANSI, if :PRINT is :top-level-forms, a message
1596 per top level form after macroexpansion is printed to *STANDARD-OUTPUT*.
1597 For example, compiling an IN-PACKAGE form will result in a message about
1598 a top level SETQ in addition to the message about the IN-PACKAGE form'
1599 itself.
1601 Both forms of reporting obey the SB-EXT:*COMPILER-PRINT-VARIABLE-ALIST*.
1603 :BLOCK-COMPILE
1604 Though COMPILE-FILE accepts an additional :BLOCK-COMPILE
1605 argument, it is not currently supported. (non-standard)
1607 :TRACE-FILE
1608 If given, internal data structures are dumped to the specified
1609 file, or if a value of T is given, to a file of *.trace type
1610 derived from the input file name. (non-standard)"
1611 ;;; Block compilation is currently broken.
1612 #|
1613 "Also, as a workaround for vaguely-non-ANSI behavior, the
1614 :BLOCK-COMPILE argument is quasi-supported, to determine whether
1615 multiple functions are compiled together as a unit, resolving function
1616 references at compile time. NIL means that global function names are
1617 never resolved at compilation time. Currently NIL is the default
1619 of the ANSI spec allows this behavior under all circumstances, the
1620 compiler's runtime scales badly when it tries to do this for large
1621 files. If/when this performance problem is fixed, the block
1622 compilation default behavior will probably be made dependent on the
1623 SPEED and COMPILATION-SPEED optimization values, and the
1624 :BLOCK-COMPILE argument will probably become deprecated."
1625 |#
1649 default-trace-file-pathname
1651 default-trace-file-pathname))))
1660 dummy)
1681 ;; Hack around filesystem race condition...
1683 nil)
1684 warnings-p
1685 failure-p)))
1686 \f
1687 ;;; a helper function for COMPILE-FILE-PATHNAME: the default for
1688 ;;; the OUTPUT-FILE argument
1689 ;;;
1690 ;;; ANSI: The defaults for the OUTPUT-FILE are taken from the pathname
1691 ;;; that results from merging the INPUT-FILE with the value of
1692 ;;; *DEFAULT-PATHNAME-DEFAULTS*, except that the type component should
1693 ;;; default to the appropriate implementation-defined default type for
1694 ;;; compiled files.
1698 retyped))
1700 ;;; KLUDGE: Part of the ANSI spec for this seems contradictory:
1701 ;;; If INPUT-FILE is a logical pathname and OUTPUT-FILE is unsupplied,
1702 ;;; the result is a logical pathname. If INPUT-FILE is a logical
1703 ;;; pathname, it is translated into a physical pathname as if by
1704 ;;; calling TRANSLATE-LOGICAL-PATHNAME.
1705 ;;; So I haven't really tried to make this precisely ANSI-compatible
1706 ;;; at the level of e.g. whether it returns logical pathname or a
1707 ;;; physical pathname. Patches to make it more correct are welcome.
1708 ;;; -- WHN 2000-12-09
1710 &key
1713 #!+sb-doc
1714 "Return a pathname describing what file COMPILE-FILE would write to given
1715 these arguments."
1719 \f
1720 ;;;; MAKE-LOAD-FORM stuff
1722 ;;; The entry point for MAKE-LOAD-FORM support. When IR1 conversion
1723 ;;; finds a constant structure, it invokes this to arrange for proper
1724 ;;; dumping. If it turns out that the constant has already been
1725 ;;; dumped, then we don't need to do anything.
1726 ;;;
1727 ;;; If the constant hasn't been dumped, then we check to see whether
1728 ;;; we are in the process of creating it. We detect this by
1729 ;;; maintaining the special *CONSTANTS-BEING-CREATED* as a list of all
1730 ;;; the constants we are in the process of creating. Actually, each
1731 ;;; entry is a list of the constant and any init forms that need to be
1732 ;;; processed on behalf of that constant.
1733 ;;;
1734 ;;; It's not necessarily an error for this to happen. If we are
1735 ;;; processing the init form for some object that showed up *after*
1736 ;;; the original reference to this constant, then we just need to
1737 ;;; defer the processing of that init form. To detect this, we
1738 ;;; maintain *CONSTANTS-CREATED-SINCE-LAST-INIT* as a list of the
1739 ;;; constants created since the last time we started processing an
1740 ;;; init form. If the constant passed to emit-make-load-form shows up
1741 ;;; in this list, then there is a circular chain through creation
1742 ;;; forms, which is an error.
1743 ;;;
1744 ;;; If there is some intervening init form, then we blow out of
1745 ;;; processing it by throwing to the tag PENDING-INIT. The value we
1746 ;;; throw is the entry from *CONSTANTS-BEING-CREATED*. This is so the
1747 ;;; offending init form can be tacked onto the init forms for the
1748 ;;; circular object.
1749 ;;;
1750 ;;; If the constant doesn't show up in *CONSTANTS-BEING-CREATED*, then
1751 ;;; we have to create it. We call MAKE-LOAD-FORM and check to see
1752 ;;; whether the creation form is the magic value
1753 ;;; :SB-JUST-DUMP-IT-NORMALLY. If it is, then we don't do anything. The
1754 ;;; dumper will eventually get its hands on the object and use the
1755 ;;; normal structure dumping noise on it.
1756 ;;;
1757 ;;; Otherwise, we bind *CONSTANTS-BEING-CREATED* and
1758 ;;; *CONSTANTS-CREATED-SINCE- LAST-INIT* and compile the creation form
1759 ;;; much the way LOAD-TIME-VALUE does. When this finishes, we tell the
1760 ;;; dumper to use that result instead whenever it sees this constant.
1761 ;;;
1762 ;;; Now we try to compile the init form. We bind
1763 ;;; *CONSTANTS-CREATED-SINCE-LAST-INIT* to NIL and compile the init
1764 ;;; form (and any init forms that were added because of circularity
1765 ;;; detection). If this works, great. If not, we add the init forms to
1766 ;;; the init forms for the object that caused the problems and let it
1767 ;;; deal with it.
1770 ;;; FIXME: Shouldn't these^ variables be unbound outside LET forms?
1774 ;; KLUDGE: This special hack is because I was too lazy
1775 ;; to rework DEF!STRUCT so that the MAKE-LOAD-FORM
1776 ;; function of LAYOUT returns nontrivial forms when
1777 ;; building the cross-compiler but :IGNORE-IT when
1778 ;; cross-compiling or running under the target Lisp. --
1779 ;; WHN 19990914
1792 (:sb-just-dump-it-normally
1794 t)
1795 (:ignore-it
1796 nil)
1811 constant
1813 creation-form)
1815 nil)
1817 constant)))
1823 collect name into names
1824 collect form into forms
1826 nil)))
1831 \f
1832 ;;;; Host compile time definitions
1833 #+sb-xc-host
1838 #+sb-xc-host