| blob | 576b18893e25420f8cebd1926f0ac252fa2d76ab |
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.
41 ;;; Set to NIL to disable loop analysis for register allocation.
44 ;;; Bind this to a stream to capture various internal debugging output.
47 ;;; The current block compilation state. These are initialized to the
48 ;;; :BLOCK-COMPILE and :ENTRY-POINTS arguments that COMPILE-FILE was
49 ;;; called with.
50 ;;;
51 ;;; *BLOCK-COMPILE-ARG* holds the original value of the :BLOCK-COMPILE
52 ;;; argument, which overrides any internal declarations.
59 ;;; When block compiling, used by PROCESS-FORM to accumulate top level
60 ;;; lambdas resulting from compiling subforms. (In reverse order.)
64 ;;; The current non-macroexpanded toplevel form as printed when
65 ;;; *compile-print* is true.
69 #!+sb-doc
72 #!+sb-doc
75 #!+sb-doc
76 "When this is true, the compiler prints to *STANDARD-OUTPUT* progress
77 information about the phases of compilation of each function. (This
81 #!+sb-doc
82 "The defaulted pathname of the file currently being compiled, or NIL if not
85 #!+sb-doc
86 "The TRUENAME of the file currently being compiled, or NIL if not
93 ;;; the SOURCE-INFO structure for the current compilation. This is
94 ;;; null globally to indicate that we aren't currently in any
95 ;;; identifiable compilation.
98 ;;; This is true if we are within a WITH-COMPILATION-UNIT form (which
99 ;;; normally causes nested uses to be no-ops).
102 ;;; Count of the number of compilation units dynamically enclosed by
103 ;;; the current active WITH-COMPILATION-UNIT that were unwound out of.
106 ;;; Mumble conditional on *COMPILE-PROGRESS*.
120 ;; Used during compilation to map code paths to the matching
121 ;; instrumentation conses.
123 ;; Used during compilation to keep track of with source paths have been
124 ;; instrumented in which blocks.
126 ;; Stores the code coverage instrumentation results. Keys are namestrings,
127 ;; the value is a list of (CONS PATH STATE), where STATE is NIL for
128 ;; a path that has not been visited, and T for one that has.
131 \f
132 ;;;; WITH-COMPILATION-UNIT and WITH-COMPILATION-VALUES
135 #!+sb-doc
136 "WITH-COMPILATION-UNIT ({Key Value}*) Form*
137 This form affects compilations that take place within its dynamic extent. It
138 is intended to be wrapped around the compilation of all files in the same
139 system. These keywords are defined:
141 :OVERRIDE Boolean-Form
142 One of the effects of this form is to delay undefined warnings
143 until the end of the form, instead of giving them at the end of each
144 compilation. If OVERRIDE is NIL (the default), then the outermost
145 WITH-COMPILATION-UNIT form grabs the undefined warnings. Specifying
146 OVERRIDE true causes that form to grab any enclosed warnings, even if
147 it is enclosed by another WITH-COMPILATION-UNIT.
149 :SOURCE-PLIST Plist-Form
150 Attaches the value returned by the Plist-Form to internal debug-source
151 information of functions compiled in within the dynamic contour.
152 Primarily for use by development environments, in order to eg. associate
153 function definitions with editor-buffers. Can be accessed as
154 SB-INTROSPECT:DEFINITION-SOURCE-PLIST. If multiple, nested
155 WITH-COMPILATION-UNITs provide :SOURCE-PLISTs, they are appended
156 togather, innermost left. If Unaffected by :OVERRIDE."
166 ;; Inside another WITH-COMPILATION-UNIT, a WITH-COMPILATION-UNIT is
167 ;; ordinarily (unless OVERRIDE) basically a no-op.
191 ;;; Is FUN-NAME something that no conforming program can rely on
192 ;;; defining as a function?
197 ;;; This is to be called at the end of a compilation unit. It signals
198 ;;; any residual warnings about unknown stuff, then prints the total
199 ;;; error counts. ABORT-P should be true when the compilation unit was
200 ;;; aborted by throwing out. ABORT-COUNT is the number of dynamically
201 ;;; enclosed nested compilation units that were aborted.
222 #+sb-xc-host nil
226 "~@<There is no function named ~S. References to ~S in ~
227 some contexts (like starts of blocks) have special ~
228 meaning, but here it would have to be a function, ~
229 and that shouldn't be right.~:@>"
230 name name))
233 "~@<The ~(~A~) ~S is undefined, and its name is ~
234 reserved by ANSI CL so that even if it were ~
235 defined later, the code doing so would not be ~
236 portable.~:@>"
237 kind name)))
246 "~W more use~:P of undefined ~(~A~) ~S"
247 more kind name)
249 "~W more use~:P of undefined ~(~A~) ~S"
250 more kind name)))))))
259 "~:[This ~(~A~) is~;These ~(~A~)s are~] undefined:~
260 ~% ~{~<~% ~1:;~S~>~^ ~}"
263 "~:[This ~(~A~) is~;These ~(~A~)s are~] undefined:~
264 ~% ~{~<~% ~1:;~S~>~^ ~}"
275 ~[~:;~:*~& caught ~W fatal ERROR condition~:P~]~
276 ~[~:;~:*~& caught ~W ERROR condition~:P~]~
277 ~[~:;~:*~& caught ~W WARNING condition~:P~]~
278 ~[~:;~:*~& caught ~W STYLE-WARNING condition~:P~]~
279 ~[~:;~:*~& printed ~W note~:P~]"
280 abort-p
289 ;;; Evaluate BODY, then return (VALUES BODY-VALUE WARNINGS-P
290 ;;; FAILURE-P), where BODY-VALUE is the first value of the body, and
291 ;;; WARNINGS-P and FAILURE-P are as in CL:COMPILE or CL:COMPILE-FILE.
292 ;;; This also wraps up WITH-IR1-NAMESPACE functionality.
300 \f
301 ;;;; component compilation
304 #!+sb-doc
305 "The upper limit on the number of times that we will consecutively do IR1
306 optimization that doesn't introduce any new code. A finite limit is
312 ;;; Repeatedly optimize COMPONENT until no further optimizations can
313 ;;; be found or we hit our iteration limit. When we hit the limit, we
314 ;;; clear the component and block REOPTIMIZE flags to discourage the
315 ;;; next optimization attempt from pounding on the same code.
359 ;;; KLUDGE: This was bumped from 5 to 10 in a DTC patch ported by MNA
360 ;;; from CMU CL into sbcl-0.6.11.44, the same one which allowed IR1
361 ;;; transforms to be delayed. Either DTC or MNA or both didn't explain
362 ;;; why, and I don't know what the rationale was. -- WHN 2001-04-28
363 ;;;
364 ;;; FIXME: It would be good to document why it's important to have a
365 ;;; large value here, and what the drawbacks of an excessively large
366 ;;; value are; and it might also be good to make it depend on
367 ;;; optimization policy.
373 ;;; Iterate doing FIND-DFO until no new dead code is discovered.
386 ;;; Do all the IR1 phases for a non-top-level component.
412 ;; We delay the generation of type checks until
413 ;; the type constraints have had time to
414 ;; propagate, else the compiler can confuse itself.
444 ;; Assign BLOCK-NUMBER for any cleanup blocks introduced by
445 ;; stack analysis. There shouldn't be any unreachable code after
446 ;; control, so this won't delete anything.
494 #-sb-xc-host
506 code-length
507 trace-table
508 fixup-notes
514 code-length
515 trace-table
516 fixup-notes
520 ;; We're done, so don't bother keeping anything around.
525 ;;; Delete components with no external entry points before we try to
526 ;;; generate code. Unreachable closures can cause IR2 conversion to
527 ;;; puke on itself, since it is the reference to the closure which
528 ;;; normally causes the components to be combined.
535 (:external
543 ;; miscellaneous sanity checks
544 ;;
545 ;; FIXME: These are basically pretty wimpy compared to the checks done
546 ;; by the old CHECK-IR1-CONSISTENCY code. It would be really nice to
547 ;; make those internal consistency checks work again and use them.
552 ;; sanity check to prevent weirdness from propagating insidiously as
553 ;; far from its root cause as it did in bug 138: Make sure that
554 ;; thing-to-COMPONENT links are consistent.
560 ;; Record xref information before optimization. This way the
561 ;; stored xref data reflects the real source as closely as
562 ;; possible.
572 #|
584 |#
586 ;; FIXME: What is MAYBE-MUMBLE for? Do we need it any more?
600 \f
601 ;;;; clearing global data structures
602 ;;;;
603 ;;;; FIXME: Is it possible to get rid of this stuff, getting rid of
604 ;;;; global data structures entirely when possible and consing up the
605 ;;;; others from scratch instead of clearing and reusing them?
607 ;;; Clear the INFO in constants in the *FREE-VARS*, etc. In
608 ;;; addition to allowing stuff to be reclaimed, this is required for
609 ;;; correct assignment of constant offsets, since we need to assign a
610 ;;; new offset for each component. We don't clear the FUNCTIONAL-INFO
611 ;;; slots, since they are used to keep track of functions across
612 ;;; component boundaries.
625 ;;; Blow away the REFS for all global variables, and let COMPONENT
626 ;;; be recycled.
638 x))
646 ;;; Clear global variables used by the compiler.
647 ;;;
648 ;;; FIXME: It seems kinda nasty and unmaintainable to have to do this,
649 ;;; and it adds overhead even when people aren't using the compiler.
650 ;;; Perhaps we could make these global vars unbound except when
651 ;;; actually in use, so that this function could go away.
654 ;; Clear global tables.
660 ;; Clear debug counters and tables.
676 ;; (Note: The CMU CL code used to set CL::*GENSYM-COUNTER* to zero here.
677 ;; Superficially, this seemed harmful -- the user could reasonably be
678 ;; surprised if *GENSYM-COUNTER* turned back to zero when something was
679 ;; compiled. A closer inspection showed that this actually turned out to be
680 ;; harmless in practice, because CLEAR-STUFF was only called from within
681 ;; forms which bound CL::*GENSYM-COUNTER* to zero. However, this means that
682 ;; even though zeroing CL::*GENSYM-COUNTER* here turned out to be harmless in
683 ;; practice, it was also useless in practice. So we don't do it any more.)
686 \f
687 ;;;; trace output
689 ;;; Print out some useful info about COMPONENT to STREAM.
710 \f
711 ;;;; file reading
712 ;;;;
713 ;;;; When reading from a file, we have to keep track of some source
714 ;;;; information. We also exploit our ability to back up for printing
715 ;;;; the error context and for recovering from errors.
716 ;;;;
717 ;;;; The interface we provide to this stuff is the stream-oid
718 ;;;; SOURCE-INFO structure. The bookkeeping is done as a side effect
719 ;;;; of getting the next source form.
721 ;;; A FILE-INFO structure holds all the source information for a
722 ;;; given file.
724 ;; If a file, the truename of the corresponding source file. If from
725 ;; a Lisp form, :LISP. If from a stream, :STREAM.
727 ;; the external format that we'll call OPEN with, if NAME is a file.
729 ;; the defaulted, but not necessarily absolute file name (i.e. prior
730 ;; to TRUENAME call.) Null if not a file. This is used to set
731 ;; *COMPILE-FILE-PATHNAME*, and if absolute, is dumped in the
732 ;; debug-info.
734 ;; the file's write date (if relevant)
736 ;; the source path root number of the first form in this file (i.e.
737 ;; the total number of forms converted previously in this
738 ;; compilation)
740 ;; parallel vectors containing the forms read out of the file and
741 ;; the file positions that reading of each form started at (i.e. the
742 ;; end of the previous form)
746 ;;; The SOURCE-INFO structure provides a handle on all the source
747 ;;; information for an entire compilation.
749 #-no-ansi-print-object
753 ;; the UT that compilation started at
755 ;; the FILE-INFO structure for this compilation
757 ;; the stream that we are using to read the FILE-INFO, or NIL if
758 ;; no stream has been opened yet
761 ;;; Given a pathname, return a SOURCE-INFO structure.
765 :external-format external-format
770 ;;; Return a SOURCE-INFO to describe the incremental compilation of FORM.
777 ;;; Return a SOURCE-INFO which will read from STREAM.
783 ;;; Return a form read from STREAM; or for EOF use the trick,
784 ;;; popularized by Kent Pitman, of returning STREAM itself. If an
785 ;;; error happens, then convert it to standard abort-the-compilation
786 ;;; error condition (possibly recording some extra location
787 ;;; information).
792 :condition condition
793 ;; We don't need to supply :POSITION here because
794 ;; READER-ERRORs already know their position in the file.
795 ))
796 ;; ANSI, in its wisdom, says that READ should return END-OF-FILE
797 ;; (and that this is not a READER-ERROR) when it encounters end of
798 ;; file in the middle of something it's trying to read.
801 :condition condition
802 ;; We need to supply :POSITION here because the END-OF-FILE
803 ;; condition doesn't carry the position that the user
804 ;; probably cares about, where the failed READ began.
807 ;;; If STREAM is present, return it, otherwise open a stream to the
808 ;;; current file. There must be a current file.
809 ;;;
810 ;;; FIXME: This is probably an unnecessarily roundabout way to do
811 ;;; things now that we process a single file in COMPILE-FILE (unlike
812 ;;; the old CMU CL code, which accepted multiple files). Also, the old
813 ;;; comment said
814 ;;; When we open a new file, we also reset *PACKAGE* and policy.
815 ;;; This gives the effect of rebinding around each file.
816 ;;; which doesn't seem to be true now. Check to make sure that if
817 ;;; such rebinding is necessary, it's still done somewhere.
830 ;;; Close the stream in INFO if it is open.
838 ;;; Read and compile the source file.
855 nil)))))))
857 ;;; Return the INDEX'th source form read from INFO and the position
858 ;;; where it was read.
864 \f
865 ;;;; processing of top level forms
867 ;;; This is called by top level form processing when we are ready to
868 ;;; actually compile something. If *BLOCK-COMPILE* is T, then we still
869 ;;; convert the form, but delay compilation, pushing the result on
870 ;;; *TOPLEVEL-LAMBDAS* instead.
874 ;; Don't bother to compile simple objects that just sit there.
887 nil)))))
889 ;;; Macroexpand FORM in the current environment with an error handler.
890 ;;; We only expand one level, so that we retain all the intervening
891 ;;; forms in the source path.
899 condition))))
901 ;;; Process a PROGN-like portion of a top level form. FORMS is a list of
902 ;;; the forms, and PATH is the source path of the FORM they came out of.
903 ;;; COMPILE-TIME-TOO is as in ANSI "3.2.3.1 Processing of Top Level Forms".
909 ;;; Process a top level use of LOCALLY, or anything else (e.g.
910 ;;; MACROLET) at top level which has declarations and ordinary forms.
911 ;;; We parse declarations and then recursively process the body.
917 ;; FIXME: VALUES declaration
918 ;;
919 ;; Binding *POLICY* is pretty much of a hack, since it
920 ;; causes LOCALLY to "capture" enclosed proclamations. It
921 ;; is necessary because CONVERT-AND-MAYBE-COMPILE uses the
922 ;; value of *POLICY* as the policy. The need for this hack
923 ;; is due to the quirk that there is no way to represent in
924 ;; a POLICY that an optimize quality came from the default.
925 ;;
926 ;; FIXME: Ideally, something should be done so that DECLAIM
927 ;; inside LOCALLY works OK. Failing that, at least we could
928 ;; issue a warning instead of silently screwing up.
930 ;; This is probably also a hack
932 ;; ditto
936 ;;; Parse an EVAL-WHEN situations list, returning three flags,
937 ;;; (VALUES COMPILE-TOPLEVEL LOAD-TOPLEVEL EXECUTE), indicating
938 ;;; the types of situations present in the list.
942 '(:compile-toplevel
943 compile
944 :load-toplevel
945 load
946 :execute
947 eval)))
952 deprecated-names)))
954 situations)
959 ;;; utilities for extracting COMPONENTs of FUNCTIONALs
970 result))))
974 result))))
977 &key
978 name
980 ;; I'd thought NIL should
981 ;; work, but it doesn't.
982 ;; -- WHN 2001-09-20
993 lambda-expression
995 ;; Convert the XEP using the policy of the real
996 ;; function. Otherwise the wrong policy will be used for
997 ;; deciding whether to type-check the parameters of the
998 ;; real function (via CONVERT-CALL / PROPAGATE-TO-ARGS).
999 ;; -- JES, 2007-02-27
1003 :source-name source-name
1011 fun)))
1013 ;;; Compile LAMBDA-EXPRESSION into *COMPILE-OBJECT*, returning a
1014 ;;; description of the result.
1015 ;;; * If *COMPILE-OBJECT* is a CORE-OBJECT, then write the function
1016 ;;; into core and return the compiled FUNCTION value.
1017 ;;; * If *COMPILE-OBJECT* is a fasl file, then write the function
1018 ;;; into the fasl file and return a dump handle.
1019 ;;;
1020 ;;; If NAME is provided, then we try to use it as the name of the
1021 ;;; function for debugging/diagnostic information.
1024 &key
1025 name
1027 ;; This magical idiom seems to be the appropriate
1028 ;; path for compiling standalone LAMBDAs, judging
1029 ;; from the CMU CL code and experiment, so it's a
1030 ;; nice default for things where we don't have a
1031 ;; real source path (as in e.g. inside CL:COMPILE).
1041 :name name
1044 ;; FIXME: The compile-it code from here on is sort of a
1045 ;; twisted version of the code in COMPILE-TOPLEVEL. It'd be
1046 ;; better to find a way to share the code there; or
1047 ;; alternatively, to use this code to replace the code there.
1048 ;; (The second alternative might be pretty easy if we used
1049 ;; the :LOCALL-ONLY option to IR1-FOR-LAMBDA. Then maybe the
1050 ;; whole FUNCTIONAL-KIND=:TOPLEVEL case could go away..)
1068 result
1069 ;; KLUDGE: This code duplicates some other code in this
1070 ;; file. In the great reorganzation, the flow of program
1071 ;; logic changed from the original CMUCL model, and that
1072 ;; path (as of sbcl-0.7.5 in SUB-COMPILE-FILE) was no
1073 ;; longer followed for CORE-OBJECTS, leading to BUG
1074 ;; 156. This place is transparently not the right one for
1075 ;; this code, but I don't have a clear enough overview of
1076 ;; the compiler to know how to rearrange it all so that
1077 ;; this operation fits in nicely, and it was blocking
1078 ;; reimplementation of (DECLAIM (INLINE FOO)) (MACROLET
1079 ;; ((..)) (DEFUN FOO ...))
1080 ;;
1081 ;; FIXME: This KLUDGE doesn't solve all the problem in an
1082 ;; ideal way, as (1) definitions typed in at the REPL
1083 ;; without an INLINE declaration will give a NULL
1084 ;; FUNCTION-LAMBDA-EXPRESSION (allowable, but not ideal)
1085 ;; and (2) INLINE declarations will yield a
1086 ;; FUNCTION-LAMBDA-EXPRESSION headed by
1087 ;; SB-C:LAMBDA-WITH-LEXENV, even for null LEXENV. -- CSR,
1088 ;; 2002-07-02
1089 ;;
1090 ;; (2) is probably fairly easy to fix -- it is, after all,
1091 ;; a matter of list manipulation (or possibly of teaching
1092 ;; CL:FUNCTION about SB-C:LAMBDA-WITH-LEXENV). (1) is
1093 ;; significantly harder, as the association between
1094 ;; function object and source is a tricky one.
1095 ;;
1096 ;; FUNCTION-LAMBDA-EXPRESSION "works" (i.e. returns a
1097 ;; non-NULL list) when the function in question has been
1098 ;; compiled by (COMPILE <x> '(LAMBDA ...)); it does not
1099 ;; work when it has been compiled as part of the top-level
1100 ;; EVAL strategy of compiling everything inside (LAMBDA ()
1101 ;; ...). -- CSR, 2002-11-02
1113 (%compile lambda-expression
1115 :name name
1129 form)
1138 form)
1142 ;;; Process a top level FORM with the specified source PATH.
1143 ;;; * If this is a magic top level form, then do stuff.
1144 ;;; * If this is a macro, then expand it.
1145 ;;; * Otherwise, just compile it.
1146 ;;;
1147 ;;; COMPILE-TIME-TOO is as defined in ANSI
1148 ;;; "3.2.3.1 Processing of Top Level Forms".
1158 path)
1163 ;; When we're cross-compiling, consider: what should we
1164 ;; do when we hit e.g.
1165 ;; (EVAL-WHEN (:COMPILE-TOPLEVEL)
1166 ;; (DEFUN FOO (X) (+ 7 X)))?
1167 ;; DEFUN has a macro definition in the cross-compiler,
1168 ;; and a different macro definition in the target
1169 ;; compiler. The only sensible thing is to use the
1170 ;; target compiler's macro definition, since the
1171 ;; cross-compiler's macro is in general into target
1172 ;; functions which can't meaningfully be executed at
1173 ;; cross-compilation time. So make sure we do the EVAL
1174 ;; here, before we macroexpand.
1175 ;;
1176 ;; Then things get even dicier with something like
1177 ;; (DEFCONSTANT-EQX SB!XC:LAMBDA-LIST-KEYWORDS ..)
1178 ;; where we have to make sure that we don't uncross
1179 ;; the SB!XC: prefix before we do EVAL, because otherwise
1180 ;; we'd be trying to redefine the cross-compilation host's
1181 ;; constants.
1182 ;;
1183 ;; (Isn't it fun to cross-compile Common Lisp?:-)
1184 #+sb-xc-host
1189 ;; like SB!XC:DEFCONSTANT and SB!XC:DEFTYPE
1190 ;; should be equivalent to their CL: counterparts
1191 ;; when being compiled as target code. We leave
1192 ;; the rest of the form uncrossed because macros
1193 ;; might yet expand into EVAL-WHEN stuff, and
1194 ;; things inside EVAL-WHEN can't be uncrossed
1195 ;; until after we've EVALed them in the
1196 ;; cross-compilation host.)
1200 slightly-uncrossed)))
1202 ;; (Now that we're no longer processing toplevel
1203 ;; forms, and hence no longer need to worry about
1204 ;; EVAL-WHEN, we can uncross everything.)
1206 ;; (We have to demote COMPILE-TIME-TOO to NIL
1207 ;; here, no matter what it was before, since
1208 ;; otherwise we'd tend to EVAL subforms more than
1209 ;; once, because of WHEN COMPILE-TIME-TOO form
1210 ;; above.)
1212 ;; When we're not cross-compiling, we only need to
1213 ;; macroexpand once, so we can follow the 1-thru-6
1214 ;; sequence of steps in ANSI's "3.2.3.1 Processing of
1215 ;; Top Level Forms".
1216 #-sb-xc-host
1226 path
1227 compile-time-too)))))))
1229 #+sb-xc-host
1230 ;; (There are no xc EVAL-WHEN issues in the ATOM case until
1231 ;; (1) SBCL gets smart enough to handle global
1232 ;; DEFINE-SYMBOL-MACRO or SYMBOL-MACROLET and (2) SBCL
1233 ;; implementors start using symbol macros in a way which
1234 ;; interacts with SB-XC/CL distinction.)
1236 #-sb-xc-host
1242 form))))
1244 ;; In the cross-compiler, top level COLD-FSET arranges
1245 ;; for static linking at cold init time.
1246 #+sb-xc-host
1252 lambda-expression
1253 path)))
1259 ;; CT, LT, and E here are as in Figure 3-7 of ANSI
1260 ;; "3.2.3.1 Processing of Top Level Forms".
1265 e))))
1267 body path new-compile-time-too))
1273 magic
1278 path
1279 compile-time-too))
1283 magic
1287 path
1288 compile-time-too
1298 \f
1299 ;;;; load time value support
1300 ;;;;
1301 ;;;; (See EMIT-MAKE-LOAD-FORM.)
1303 ;;; Return T if we are currently producing a fasl file and hence
1304 ;;; constants need to be dumped carefully.
1308 ;;; Compile FORM and arrange for it to be called at load-time. Return
1309 ;;; the dumper handle and our best guess at the type of the object.
1319 ;;; Compile the FORMS and arrange for them to be called (for effect,
1320 ;;; not value) at load time.
1325 ;;; Do the actual work of COMPILE-LOAD-TIME-VALUE or
1326 ;;; COMPILE-MAKE-LOAD-FORM-INIT-FORMS.
1332 lambda)))
1334 ;;; This is called by COMPILE-TOPLEVEL when it was passed T for
1335 ;;; LOAD-TIME-VALUE-P (which happens in COMPILE-LOAD-TIME-STUFF). We
1336 ;;; don't try to combine this component with anything else and frob
1337 ;;; the name. If not in a :TOPLEVEL component, then don't bother
1338 ;;; compiling, because it was merged with a run-time component.
1347 \f
1348 ;;;; COMPILE-FILE
1358 ;;; Smash LAMBDAS into a single component, compile it, and arrange for
1359 ;;; the resulting function to be called.
1369 ;;; Compile top level code and call the top level lambdas. We pick off
1370 ;;; top level lambdas in non-top-level components here, calling
1371 ;;; SUB-c-t-l-l on each subsequence of normal top level lambdas.
1380 lambdas
1381 ;; this used to read ":start start", but
1382 ;; start can be greater than len, which
1383 ;; is an error according to ANSI - CSR,
1384 ;; 2002-04-25
1386 len)))
1395 ;;; Compile LAMBDAS (a list of CLAMBDAs for top level forms) into the
1396 ;;; object file.
1397 ;;;
1398 ;;; LOAD-TIME-VALUE-P seems to control whether it's MAKE-LOAD-FORM and
1399 ;;; COMPILE-LOAD-TIME-VALUE stuff. -- WHN 20000201
1433 ;;; Actually compile any stuff that has been queued up for block
1434 ;;; compilation.
1454 lexenv))
1458 nil
1474 lexenv))
1484 ;;; Read all forms from INFO and compile them, with output to OBJECT.
1485 ;;; Return (VALUES ABORT-P WARNINGS-P FAILURE-P).
1514 ;; FIXME: Do we need this rebinding here? It's a literal
1515 ;; translation of the old CMU CL rebinding to
1516 ;; (OR *BACKEND-INFO-ENVIRONMENT* *INFO-ENVIRONMENT*),
1517 ;; and it's not obvious whether the rebinding to itself is
1518 ;; needed that SBCL doesn't need *BACKEND-INFO-ENVIRONMENT*.
1531 ;; Dump the code coverage records into the fasl.
1539 list))
1540 nil
1541 nil))
1549 nil)))
1550 ;; Some errors are sufficiently bewildering that we just fail
1551 ;; immediately, without trying to recover and compile more of
1552 ;; the input file.
1557 "~@<compilation aborted because of fatal error: ~2I~_~A~:>"
1558 condition))
1562 ;;; Return a pathname for the named file. The file must exist.
1571 new
1584 ;;; Print some junk at the beginning and end of compilation.
1592 file-info)
1594 :print-weekday nil
1601 won
1607 ;;; Open some files and call SUB-COMPILE-FILE. If something unwinds
1608 ;;; out of the compile, then abort the writing of the output file, so
1609 ;;; that we don't overwrite it with known garbage.
1612 &key
1614 ;; ANSI options
1616 ;; FIXME: ANSI doesn't seem to say anything about
1617 ;; *COMPILE-VERBOSE* and *COMPILE-PRINT* being rebound by this
1618 ;; function..
1623 ;; extensions
1626 #!+sb-doc
1627 "Compile INPUT-FILE, producing a corresponding fasl file and
1628 returning its filename.
1630 :PRINT
1631 If true, a message per non-macroexpanded top level form is printed
1632 to *STANDARD-OUTPUT*. Top level forms that whose subforms are
1633 processed as top level forms (eg. EVAL-WHEN, MACROLET, PROGN) receive
1634 no such message, but their subforms do.
1636 As an extension to ANSI, if :PRINT is :top-level-forms, a message
1637 per top level form after macroexpansion is printed to *STANDARD-OUTPUT*.
1638 For example, compiling an IN-PACKAGE form will result in a message about
1639 a top level SETQ in addition to the message about the IN-PACKAGE form'
1640 itself.
1642 Both forms of reporting obey the SB-EXT:*COMPILER-PRINT-VARIABLE-ALIST*.
1644 :BLOCK-COMPILE
1645 Though COMPILE-FILE accepts an additional :BLOCK-COMPILE
1646 argument, it is not currently supported. (non-standard)
1648 :TRACE-FILE
1649 If given, internal data structures are dumped to the specified
1650 file, or if a value of T is given, to a file of *.trace type
1651 derived from the input file name. (non-standard)"
1652 ;;; Block compilation is currently broken.
1653 #|
1654 "Also, as a workaround for vaguely-non-ANSI behavior, the
1655 :BLOCK-COMPILE argument is quasi-supported, to determine whether
1656 multiple functions are compiled together as a unit, resolving function
1657 references at compile time. NIL means that global function names are
1658 never resolved at compilation time. Currently NIL is the default
1660 of the ANSI spec allows this behavior under all circumstances, the
1661 compiler's runtime scales badly when it tries to do this for large
1662 files. If/when this performance problem is fixed, the block
1663 compilation default behavior will probably be made dependent on the
1664 SPEED and COMPILATION-SPEED optimization values, and the
1665 :BLOCK-COMPILE argument will probably become deprecated."
1666 |#
1690 default-trace-file-pathname
1692 default-trace-file-pathname))))
1720 ;; CLHS says that the first value is NIL if the "file could not
1721 ;; be created". We interpret this to mean "a valid fasl could not
1722 ;; be created" -- which can happen if the compilation is aborted
1723 ;; before the whole file has been processed, due to eg. a reader
1724 ;; error.
1726 ;; Hack around filesystem race condition...
1728 warnings-p
1729 failure-p)))
1730 \f
1731 ;;; a helper function for COMPILE-FILE-PATHNAME: the default for
1732 ;;; the OUTPUT-FILE argument
1733 ;;;
1734 ;;; ANSI: The defaults for the OUTPUT-FILE are taken from the pathname
1735 ;;; that results from merging the INPUT-FILE with the value of
1736 ;;; *DEFAULT-PATHNAME-DEFAULTS*, except that the type component should
1737 ;;; default to the appropriate implementation-defined default type for
1738 ;;; compiled files.
1742 retyped))
1744 ;;; KLUDGE: Part of the ANSI spec for this seems contradictory:
1745 ;;; If INPUT-FILE is a logical pathname and OUTPUT-FILE is unsupplied,
1746 ;;; the result is a logical pathname. If INPUT-FILE is a logical
1747 ;;; pathname, it is translated into a physical pathname as if by
1748 ;;; calling TRANSLATE-LOGICAL-PATHNAME.
1749 ;;; So I haven't really tried to make this precisely ANSI-compatible
1750 ;;; at the level of e.g. whether it returns logical pathname or a
1751 ;;; physical pathname. Patches to make it more correct are welcome.
1752 ;;; -- WHN 2000-12-09
1754 &key
1757 #!+sb-doc
1758 "Return a pathname describing what file COMPILE-FILE would write to given
1759 these arguments."
1763 \f
1764 ;;;; MAKE-LOAD-FORM stuff
1766 ;;; The entry point for MAKE-LOAD-FORM support. When IR1 conversion
1767 ;;; finds a constant structure, it invokes this to arrange for proper
1768 ;;; dumping. If it turns out that the constant has already been
1769 ;;; dumped, then we don't need to do anything.
1770 ;;;
1771 ;;; If the constant hasn't been dumped, then we check to see whether
1772 ;;; we are in the process of creating it. We detect this by
1773 ;;; maintaining the special *CONSTANTS-BEING-CREATED* as a list of all
1774 ;;; the constants we are in the process of creating. Actually, each
1775 ;;; entry is a list of the constant and any init forms that need to be
1776 ;;; processed on behalf of that constant.
1777 ;;;
1778 ;;; It's not necessarily an error for this to happen. If we are
1779 ;;; processing the init form for some object that showed up *after*
1780 ;;; the original reference to this constant, then we just need to
1781 ;;; defer the processing of that init form. To detect this, we
1782 ;;; maintain *CONSTANTS-CREATED-SINCE-LAST-INIT* as a list of the
1783 ;;; constants created since the last time we started processing an
1784 ;;; init form. If the constant passed to emit-make-load-form shows up
1785 ;;; in this list, then there is a circular chain through creation
1786 ;;; forms, which is an error.
1787 ;;;
1788 ;;; If there is some intervening init form, then we blow out of
1789 ;;; processing it by throwing to the tag PENDING-INIT. The value we
1790 ;;; throw is the entry from *CONSTANTS-BEING-CREATED*. This is so the
1791 ;;; offending init form can be tacked onto the init forms for the
1792 ;;; circular object.
1793 ;;;
1794 ;;; If the constant doesn't show up in *CONSTANTS-BEING-CREATED*, then
1795 ;;; we have to create it. We call MAKE-LOAD-FORM and check to see
1796 ;;; whether the creation form is the magic value
1797 ;;; :SB-JUST-DUMP-IT-NORMALLY. If it is, then we don't do anything. The
1798 ;;; dumper will eventually get its hands on the object and use the
1799 ;;; normal structure dumping noise on it.
1800 ;;;
1801 ;;; Otherwise, we bind *CONSTANTS-BEING-CREATED* and
1802 ;;; *CONSTANTS-CREATED-SINCE- LAST-INIT* and compile the creation form
1803 ;;; much the way LOAD-TIME-VALUE does. When this finishes, we tell the
1804 ;;; dumper to use that result instead whenever it sees this constant.
1805 ;;;
1806 ;;; Now we try to compile the init form. We bind
1807 ;;; *CONSTANTS-CREATED-SINCE-LAST-INIT* to NIL and compile the init
1808 ;;; form (and any init forms that were added because of circularity
1809 ;;; detection). If this works, great. If not, we add the init forms to
1810 ;;; the init forms for the object that caused the problems and let it
1811 ;;; deal with it.
1814 ;;; FIXME: Shouldn't these^ variables be unbound outside LET forms?
1818 ;; KLUDGE: This special hack is because I was too lazy
1819 ;; to rework DEF!STRUCT so that the MAKE-LOAD-FORM
1820 ;; function of LAYOUT returns nontrivial forms when
1821 ;; building the cross-compiler but :IGNORE-IT when
1822 ;; cross-compiling or running under the target Lisp. --
1823 ;; WHN 19990914
1832 ;; If the constant is a reference to a named constant, we can
1833 ;; just use SYMBOL-VALUE during LOAD.
1840 (:sb-just-dump-it-normally
1842 t)
1843 (:ignore-it
1844 nil)
1857 constant
1859 creation-form)
1861 nil)
1863 constant)))
1869 collect name into names
1870 collect form into forms
1872 nil)))
1877 \f
1878 ;;;; Host compile time definitions
1879 #+sb-xc-host
1884 #+sb-xc-host