| blob | 883be9025ea9d581b33672d3cf71e9a09606f1a7 |
1 ;;;; function call for the x86 VM
3 ;;;; This software is part of the SBCL system. See the README file for
4 ;;;; more information.
5 ;;;;
6 ;;;; This software is derived from the CMU CL system, which was
7 ;;;; written at Carnegie Mellon University and released into the
8 ;;;; public domain. The software is in the public domain and is
9 ;;;; provided with absolutely no warranty. See the COPYING and CREDITS
10 ;;;; files for more information.
13 \f
14 ;;;; interfaces to IR2 conversion
16 ;;; Return a wired TN describing the N'th full call argument passing
17 ;;; location.
25 ;;; Make a passing location TN for a local call return PC.
26 ;;;
27 ;;; Always wire the return PC location to the stack in its standard
28 ;;; location.
32 sap-stack-sc-number return-pc-save-offset))
34 ;;; This is similar to MAKE-RETURN-PC-PASSING-LOCATION, but makes a
35 ;;; location to pass OLD-FP in.
36 ;;;
37 ;;; This is wired in both the standard and the local-call conventions,
38 ;;; because we want to be able to assume it's always there. Besides,
39 ;;; the x86 doesn't have enough registers to really make it profitable
40 ;;; to pass it in a register.
44 ocfp-save-offset))
46 ;;; Make the TNs used to hold OLD-FP and RETURN-PC within the current
47 ;;; function. We treat these specially so that the debugger can find
48 ;;; them at a known location.
49 ;;;
50 ;;; Without using a save-tn - which does not make much sense if it is
51 ;;; wired to the stack?
54 control-stack-sc-number
55 ocfp-save-offset)
56 physenv))
60 sap-stack-sc-number return-pc-save-offset)
61 physenv))
63 ;;; Make a TN for the standard argument count passing location. We only
64 ;;; need to make the standard location, since a count is never passed when we
65 ;;; are using non-standard conventions.
69 ;;; Make a TN to hold the number-stack frame pointer. This is allocated
70 ;;; once per component, and is component-live.
80 ;;; Return a list of TNs that can be used to represent an unknown-values
81 ;;; continuation within a function.
86 ;;; This function is called by the ENTRY-ANALYZE phase, allowing
87 ;;; VM-dependent initialization of the IR2-COMPONENT structure. We
88 ;;; push placeholder entries in the CONSTANTS to leave room for
89 ;;; additional noise in the code object header.
92 ;; The 1+ here is because for the x86 the first constant is a
93 ;; pointer to a list of fixups, or NIL if the code object has none.
94 ;; (If I understand correctly, the fixups are needed at GC copy
95 ;; time because the X86 code isn't relocatable.)
96 ;;
97 ;; KLUDGE: It'd be cleaner to have the fixups entry be a named
98 ;; element of the CODE (aka component) primitive object. However,
99 ;; it's currently a large, tricky, error-prone chore to change
100 ;; the layout of any primitive object, so for the foreseeable future
101 ;; we'll just live with this ugliness. -- WHN 2002-01-02
106 \f
107 ;;;; frame hackery
109 ;;; This is used for setting up the Old-FP in local call.
115 ;;; We don't have a separate NFP, so we don't need to do anything here.
120 nil))
129 ;; Skip space for the function header.
134 ;; The start of the actual code.
135 ;; Save the return-pc.
138 ;; If copy-more-arg follows it will allocate the correct stack
139 ;; size. The stack is not allocated first here as this may expose
140 ;; args on the stack if they take up more space than the frame!
142 ;; The args fit within the frame so just allocate the frame.
150 ;;; This is emitted directly before either a known-call-local, call-local,
151 ;;; or a multiple-call-local. All it does is allocate stack space for the
152 ;;; callee (who has the same size stack as us).
162 ;;; Allocate a partial frame for passing stack arguments in a full
163 ;;; call. NARGS is the number of arguments passed. We allocate at
164 ;;; least 3 slots, because the XEP noise is going to want to use them
165 ;;; before it can extend the stack.
172 \f
173 ;;; Emit code needed at the return-point from an unknown-values call
174 ;;; for a fixed number of values. Values is the head of the TN-REF
175 ;;; list for the locations that the values are to be received into.
176 ;;; Nvals is the number of values that are to be received (should
177 ;;; equal the length of Values).
178 ;;;
179 ;;; MOVE-TEMP is a DESCRIPTOR-REG TN used as a temporary.
180 ;;;
181 ;;; This code exploits the fact that in the unknown-values convention,
182 ;;; a single value return returns at the return PC + 2, whereas a
183 ;;; return of other than one value returns directly at the return PC.
184 ;;;
185 ;;; If 0 or 1 values are expected, then we just emit an instruction to
186 ;;; reset the SP (which will only be executed when other than 1 value
187 ;;; is returned.)
188 ;;;
189 ;;; In the general case we have to do three things:
190 ;;; -- Default unsupplied register values. This need only be done
191 ;;; when a single value is returned, since register values are
192 ;;; defaulted by the called in the non-single case.
193 ;;; -- Default unsupplied stack values. This needs to be done whenever
194 ;;; there are stack values.
195 ;;; -- Reset SP. This must be done whenever other than 1 value is
196 ;;; returned, regardless of the number of values desired.
208 ;; Default the unsupplied registers.
216 for count from 2 below register-arg-count
222 ;; The number of bytes depends on the relative jump instructions.
223 ;; Best case is 31+(n-3)*14, worst case is 35+(n-3)*18. For
224 ;; NVALS=6 that is 73/89 bytes, and for NVALS=7 that is 87/107
225 ;; bytes which is likely better than using the blt below.
230 ;; Branch off to the MV case.
232 ;; Do the single value case.
233 ;; Default the register args
240 ;; Fake other registers so it looks like we returned with all the
241 ;; registers filled in.
287 ;; Branch off to the MV case.
290 ;; Default the register args, and set up the stack as if we
291 ;; entered the MV return point.
297 ;; Compute a pointer to where to put the [defaulted] stack values.
302 ;; Load RAX with NIL so we can quickly store it, and set up
303 ;; stuff for the loop.
307 ;; Jump into the default loop.
310 ;; The regs are defaulted. We need to copy any stack arguments,
311 ;; and then default the remaining stack arguments.
313 ;; Save EDI.
315 ;; Compute the number of stack arguments, and if it's zero or
316 ;; less, don't copy any stack arguments.
320 ;; Throw away any unwanted args.
325 ;; Save the number of stack values.
327 ;; Compute a pointer to where the stack args go.
331 ;; Save ESI, and compute a pointer to where the args come from.
336 ;; Do the copy.
341 ;; Restore RSI.
343 ;; Now we have to default the remaining args. Find out how many.
346 ;; If none, then just blow out of here.
350 ;; Load RAX with NIL for fast storing.
352 ;; Do the store.
356 ;; Restore EDI, and reset the stack.
362 \f
363 ;;;; unknown values receiving
365 ;;; Emit code needed at the return point for an unknown-values call
366 ;;; for an arbitrary number of values.
367 ;;;
368 ;;; We do the single and non-single cases with no shared code: there
369 ;;; doesn't seem to be any potential overlap, and receiving a single
370 ;;; value is more important efficiency-wise.
371 ;;;
372 ;;; When there is a single value, we just push it on the stack,
373 ;;; returning the old SP and 1.
374 ;;;
375 ;;; When there is a variable number of values, we move all of the
376 ;;; argument registers onto the stack, and return ARGS and NARGS.
377 ;;;
378 ;;; ARGS and NARGS are TNs wired to the named locations. We must
379 ;;; explicitly allocate these TNs, since their lifetimes overlap with
380 ;;; the results start and count. (Also, it's nice to be able to target
381 ;;; them.)
397 ;; dtc: this writes the registers onto the stack even if they are
398 ;; not needed, only the number specified in rcx are used and have
399 ;; stack allocated to them. No harm is done.
402 for i downfrom -1
410 ;;; VOP that can be inherited by unknown values receivers. The main thing this
411 ;;; handles is allocation of the result temporaries.
415 values-start)
418 nvals)
421 \f
422 ;;;; local call with unknown values convention return
424 ;;; Non-TR local call for a fixed number of values passed according to
425 ;;; the unknown values convention.
426 ;;;
427 ;;; FP is the frame pointer in install before doing the call.
428 ;;;
429 ;;; NFP would be the number-stack frame pointer if we had a separate
430 ;;; number stack.
431 ;;;
432 ;;; Args are the argument passing locations, which are specified only
433 ;;; to terminate their lifetimes in the caller.
434 ;;;
435 ;;; VALUES are the return value locations (wired to the standard
436 ;;; passing locations). NVALS is the number of values received.
437 ;;;
438 ;;; Save is the save info, which we can ignore since saving has been
439 ;;; done.
440 ;;;
441 ;;; TARGET is a continuation pointing to the start of the called
442 ;;; function.
459 #+nil
464 ;; Is the return-pc on the stack or in a register?
476 RETURN
480 ;;; Non-TR local call for a variable number of return values passed according
481 ;;; to the unknown values convention. The results are the start of the values
482 ;;; glob and the number of values received.
498 #+nil
503 ;; Is the return-pc on the stack or in a register?
508 ;; Stack
512 ;; Register
517 RETURN
521 \f
522 ;;;; local call with known values return
524 ;;; Non-TR local call with known return locations. Known-value return
525 ;;; works just like argument passing in local call.
526 ;;;
527 ;;; Note: we can't use normal load-tn allocation for the fixed args,
528 ;;; since all registers may be tied up by the more operand. Instead,
529 ;;; we use MAYBE-LOAD-STACK-TN.
547 #+nil
552 ;; Is the return-pc on the stack or in a register?
557 ;; Stack
561 ;; Register
566 RETURN
569 \f
570 ;;; Return from known values call. We receive the return locations as
571 ;;; arguments to terminate their lifetimes in the returning function. We
572 ;;; restore FP and CSP and jump to the Return-PC.
573 ;;;
574 ;;; We can assume we know exactly where old-fp and return-pc are because
575 ;;; make-old-fp-save-location and make-return-pc-save-location always
576 ;;; return the same place.
577 #+nil
589 ;; Save the return-pc in a register 'cause the frame-pointer is
590 ;; going away. Note this not in the usual stack location so we
591 ;; can't use RET
593 ;; Restore the stack.
595 ;; Restore the old fp. We know OLD-FP is going to be in its stack
596 ;; save slot, which is a different frame that than this one,
597 ;; so we don't have to worry about having just cleared
598 ;; most of the stack.
602 \f
603 ;;; From Douglas Crosher
604 ;;; Return from known values call. We receive the return locations as
605 ;;; arguments to terminate their lifetimes in the returning function. We
606 ;;; restore FP and CSP and jump to the Return-PC.
607 ;;;
608 ;;; The old-fp may be either in a register or on the stack in its
609 ;;; standard save locations - slot 0.
610 ;;;
611 ;;; The return-pc may be in a register or on the stack in any slot.
622 ;; return-pc may be either in a register or on the stack.
628 ;; Zot all of the stack except for the old-fp.
631 n-word-bytes))))
632 ;; Restore the old fp from its save location on the stack,
633 ;; and zot the stack.
638 "VOP return-local doesn't work if old-fp (in slot ~
639 ~S) is not in slot 0"
643 ;; Zot all the stack.
645 ;; Restore the old-fp.
648 ;; Return; return-pc is in a register.
659 \f
660 ;;;; full call
661 ;;;
662 ;;; There is something of a cross-product effect with full calls.
663 ;;; Different versions are used depending on whether we know the
664 ;;; number of arguments or the name of the called function, and
665 ;;; whether we want fixed values, unknown values, or a tail call.
666 ;;;
667 ;;; In full call, the arguments are passed creating a partial frame on
668 ;;; the stack top and storing stack arguments into that frame. On
669 ;;; entry to the callee, this partial frame is pointed to by FP.
671 ;;; This macro helps in the definition of full call VOPs by avoiding
672 ;;; code replication in defining the cross-product VOPs.
673 ;;;
674 ;;; NAME is the name of the VOP to define.
675 ;;;
676 ;;; NAMED is true if the first argument is an fdefinition object whose
677 ;;; definition is to be called.
678 ;;;
679 ;;; RETURN is either :FIXED, :UNKNOWN or :TAIL:
680 ;;; -- If :FIXED, then the call is for a fixed number of values, returned in
681 ;;; the standard passing locations (passed as result operands).
682 ;;; -- If :UNKNOWN, then the result values are pushed on the stack, and the
683 ;;; result values are specified by the Start and Count as in the
684 ;;; unknown-values continuation representation.
685 ;;; -- If :TAIL, then do a tail-recursive call. No values are returned.
686 ;;; The Old-Fp and Return-PC are passed as the second and third arguments.
687 ;;;
688 ;;; In non-tail calls, the pointer to the stack arguments is passed as
689 ;;; the last fixed argument. If Variable is false, then the passing
690 ;;; locations are passed as a more arg. Variable is true if there are
691 ;;; a variable number of arguments passed on the stack. Variable
692 ;;; cannot be specified with :TAIL return. TR variable argument call
693 ;;; is implemented separately.
694 ;;;
695 ;;; In tail call with fixed arguments, the passing locations are
696 ;;; passed as a more arg, but there is no new-FP, since the arguments
697 ;;; have been set up in the current frame.
703 (:args
725 (:info
729 step-instrumenting)
731 (:ignore
735 ;; We pass either the fdefn object (for named call) or
736 ;; the actual function object (for unnamed call) in
737 ;; RAX. With named call, closure-tramp will replace it
738 ;; with the real function and invoke the real function
739 ;; for closures. Non-closures do not need this value,
740 ;; so don't care what shows up in it.
741 (:temporary
742 (:sc descriptor-reg
743 :offset rax-offset
746 rax)
748 ;; We pass the number of arguments in RCX.
751 ;; With variable call, we have to load the
752 ;; register-args out of the (new) stack frame before
753 ;; doing the call. Therefore, we have to tell the
754 ;; lifetime stuff that we need to use them.
768 old-fp-tmp)))
773 15
777 ;; This has to be done before the frame pointer is
778 ;; changed! RAX stores the 'lexical environment' needed
779 ;; for closures.
784 ;; For variable call, compute the number of
785 ;; arguments and move some of the arguments to
786 ;; registers.
788 ;; Compute the number of arguments.
791 ;; Move the necessary args to registers,
792 ;; this moves them all even if they are
793 ;; not all needed.
796 for index downfrom -1
804 ;; return to so might as well use that clue.
805 ;; This seems really important to the
806 ;; implementation of things like
807 ;; (without-interrupts ...)
808 ;;
809 ;; dtc; Could be doing a tail call from a
810 ;; known-local-call etc in which the old-fp
811 ;; or ret-pc are in regs or in non-standard
812 ;; places. If the passing location were
813 ;; wired to the stack in standard locations
814 ;; then these moves will be un-necessary;
815 ;; this is probably best for the x86.
820 ;; FIXME: FORMAT T for stale
821 ;; diagnostic output (several of
822 ;; them around here), ick
826 rbp-tn
831 rbp-tn
834 ;; For tail call, we have to push the
835 ;; return-pc so that it looks like we CALLed
836 ;; drspite the fact that we are going to JMP.
838 ))
840 ;; For non-tail call, we have to save our
841 ;; frame pointer and install the new frame
842 ;; pointer. We can't load stack tns after this
843 ;; point.
845 ;; here which doesn't leave room for the
846 ;; ofp/ret stuff.
848 ;; The variable args are on the stack and
849 ;; become the frame, but there may be <3
850 ;; args and 3 stack slots are assumed
851 ;; allocate on the call. So need to ensure
852 ;; there are at least 3 slots. This hack
853 ;; just adds 3 more.
857 ;; Save the fp
861 )))
867 DONE
875 n-word-bytes)
876 other-pointer-lowtag)
878 fun-pointer-lowtag))))
880 (:fixed
882 (:unknown
898 ;;; This is defined separately, since it needs special code that BLT's
899 ;;; the arguments down. All the real work is done in the assembly
900 ;;; routine. We just set things up so that it can find what it needs.
909 ; (:ignore ret-addr old-fp)
911 ;; Move these into the passing locations if they are not already there.
915 ;; The following assumes that the return-pc and old-fp are on the
916 ;; stack in their standard save locations - Check this.
928 ;; And jump to the assembly routine.
930 \f
931 ;;;; unknown values return
933 ;;; Return a single-value using the Unknown-Values convention. Specifically,
934 ;;; we jump to clear the stack and jump to return-pc+3.
935 ;;;
936 ;;; We require old-fp to be in a register, because we want to reset RSP before
937 ;;; restoring RBP. If old-fp were still on the stack, it could get clobbered
938 ;;; by a signal.
939 ;;;
940 ;;; pfw--get wired-tn conflicts sometimes if register sc specd for args
941 ;;; having problems targeting args to regs -- using temps instead.
949 ;; Code structure lifted from known-return.
952 ;; return PC in register for some reason (local call?)
953 ;; we jmp to the return pc after fixing the stack and frame.
956 ;; ofp on stack must be in slot 0 (the traditional storage place).
957 ;; Drop the stack above it and pop it off.
961 n-word-bytes))))
964 ;; Should this ever happen, we do the same as above, but
965 ;; using (tn-offset old-fp) instead of ocfp-save-offset
966 ;; (which is 0 anyway, see src/compiler/x86/vm.lisp) and
967 ;; then lea rsp again against itself with a displacement
968 ;; of (* (tn-offset old-fp) n-word-bytes) to clear the
969 ;; rest of the stack.
973 ;; ofp in reg, drop the stack and load the real fp.
977 ;; Set single-value-return flag
979 ;; And return
983 ;; Note that this will only work right if, when old-fp is on
984 ;; the stack, it has a lower tn-offset than return-pc. One of
985 ;; the comments in known-return indicate that this is the case
986 ;; (in that it will be in its save location), but we may wish
987 ;; to assert that (in either the weaker or stronger forms).
988 ;; Should this ever not be the case, we should load old-fp
989 ;; into a temp reg while we fix the stack.
990 ;; Drop stack above return-pc
993 n-word-bytes))))
994 ;; Set single-value return flag
996 ;; Restore the old frame pointer
998 ;; And return, dropping the rest of the stack as we go.
1001 ;;; Do unknown-values return of a fixed (other than 1) number of
1002 ;;; values. The VALUES are required to be set up in the standard
1003 ;;; passing locations. NVALS is the number of values returned.
1004 ;;;
1005 ;;; Basically, we just load RCX with the number of values returned and
1006 ;;; RBX with a pointer to the values, set RSP to point to the end of
1007 ;;; the values, and jump directly to return-pc.
1015 ;; In the case of other than one value, we need these registers to
1016 ;; tell the caller where they are and how many there are.
1020 ;; We need to stretch the lifetime of return-pc past the argument
1021 ;; registers so that we can default the argument registers without
1022 ;; trashing return-pc.
1032 ;; Establish the values pointer and values count.
1037 ;; Restore the frame pointer.
1039 ;; Clear as much of the stack as possible, but not past the return
1040 ;; address.
1043 ;; Pre-default any argument register that need it.
1050 ;; Set the multiple value return flag.
1052 ;; And away we go. Except that return-pc is still on the
1053 ;; stack and we've changed the stack pointer. So we have to
1054 ;; tell it to index off of RBX instead of RBP.
1056 ;; Return popping the return address and the OCFP.
1059 ;; Return popping the return, leaving 1 slot. Can this
1060 ;; happen, or is a single value return handled elsewhere?
1065 n-word-bytes))))))
1069 ;;; Do unknown-values return of an arbitrary number of values (passed
1070 ;;; on the stack.) We check for the common case of a single return
1071 ;;; value, and do that inline using the normal single value return
1072 ;;; convention. Otherwise, we branch off to code that calls an
1073 ;;; assembly-routine.
1074 ;;;
1075 ;;; The assembly routine takes the following args:
1076 ;;; RAX -- the return-pc to finally jump to.
1077 ;;; RBX -- pointer to where to put the values.
1078 ;;; RCX -- number of values to find there.
1079 ;;; RSI -- pointer to where to find the values.
1098 ;; Load the return-pc.
1101 ;; Check for the single case.
1106 ;; Return with one value.
1108 ;; Clear the stack. We load old-fp into a register before clearing
1109 ;; the stack.
1113 ;; clear the multiple-value return flag
1115 ;; Out of here.
1118 ;; Nope, not the single case. Jump to the assembly routine.
1129 \f
1130 ;;;; XEP hackery
1132 ;;; We don't need to do anything special for regular functions.
1137 ;; Don't bother doing anything.
1138 nil))
1140 ;;; Get the lexical environment from its passing location.
1146 ;; Get result.
1149 ;;; Copy a &MORE arg from the argument area to the end of the current
1150 ;;; frame. FIXED is the number of non-&MORE arguments.
1157 ;; Avoid the copy if there are no more args.
1164 ;; Allocate the space on the stack.
1165 ;; stack = rbp - (max 3 frame-size) - (nargs - fixed)
1169 (* n-word-bytes
1174 ;; Now: nargs>=1 && nargs>fixed
1176 ;; Save the original count of args.
1180 ;; We must stop when we run out of stack args, not when we
1181 ;; run out of more args.
1182 ;; Number to copy = nargs-3
1184 ;; Everything of interest in registers.
1187 ;; Number to copy = nargs-fixed
1190 ;; Initialize R8 to be the end of args.
1194 ;; We need to copy from downwards up to avoid overwriting some of
1195 ;; the yet uncopied args. So we need to use R9 as the copy index
1196 ;; and RCX as the loop counter, rather than using RCX for both.
1199 ;; We used to use REP MOVS here, but on modern x86 it performs
1200 ;; much worse than an explicit loop for small blocks.
1201 COPY-LOOP
1208 DO-REGS
1210 ;; Restore RCX
1213 ;; Here: nargs>=1 && nargs>fixed
1215 ;; Now we have to deposit any more args that showed up in
1216 ;; registers.
1219 ;; Store it relative to rbp
1230 ;; Don't deposit any more than there are.
1238 JUST-ALLOC-FRAME
1244 DONE))
1273 ;;; Turn more arg (context, count) into a list.
1275 t)
1296 ;; Check to see whether there are no args, and just return NIL if so.
1304 ;; Set decrement mode (successive args at lower addresses)
1306 ;; Set up the result.
1308 ;; Jump into the middle of the loop, 'cause that's where we want
1309 ;; to start.
1312 ;; Compute a pointer to the next cons.
1314 ;; Store a pointer to this cons in the CDR of the previous cons.
1317 ;; Grab one value and stash it in the car of this cons.
1320 ;; Go back for more.
1323 ;; NIL out the last cons.
1328 ;;; Return the location and size of the &MORE arg glob created by
1329 ;;; COPY-MORE-ARG. SUPPLIED is the total number of arguments supplied
1330 ;;; (originally passed in RCX). FIXED is the number of non-rest
1331 ;;; arguments.
1332 ;;;
1333 ;;; We must duplicate some of the work done by COPY-MORE-ARG, since at
1334 ;;; that time the environment is in a pretty brain-damaged state,
1335 ;;; preventing this info from being returned as values. What we do is
1336 ;;; compute supplied - fixed, and return a pointer that many words
1337 ;;; below the current stack top.
1350 ;; SP at this point points at the last arg pushed.
1351 ;; Point to the first more-arg, not above it.
1358 ;;; Signal wrong argument count error if NARGS isn't equal to COUNT.
1375 ;;; Various other error signallers.
1383 args))
1391 object type)
1393 object layout)
1400 ;;; Single-stepping
1403 ;; We use different ways of representing whether stepping is on on
1404 ;; +SB-THREAD / -SB-THREAD: on +SB-THREAD, we use a slot in the
1405 ;; thread structure. On -SB-THREAD we use the value of a static
1406 ;; symbol. Things are done this way, since reading a thread-local
1407 ;; slot from a symbol would require an extra register on +SB-THREAD,
1408 ;; and reading a slot from a thread structure would require an extra
1409 ;; register on -SB-THREAD. While this isn't critical for x86-64,
1410 ;; it's more serious for x86.
1411 #!+sb-thread
1413 :base thread-base-tn
1415 nil-value)
1416 #!-sb-thread
1422 nil-value))
1431 DONE