X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fassembly%2Fx86%2Fsupport.lisp;h=1b814f32d9c5ede3534375f119cb9c20df92e987;hb=1eb303172df6650de51ad12b993a392681f50c50;hp=1e5107962909fbba16b7f27c7a52239ab34bb3aa;hpb=4898ef32c639b1c7f4ee13a5ba566ce6debd03e6;p=sbcl.git diff --git a/src/assembly/x86/support.lisp b/src/assembly/x86/support.lisp index 1e51079..1b814f3 100644 --- a/src/assembly/x86/support.lisp +++ b/src/assembly/x86/support.lisp @@ -9,6 +9,20 @@ (in-package "SB!VM") +;;; The :full-call assembly-routines must use the same full-call +;;; unknown-values return convention as a normal call, as some +;;; of the routines will tail-chain to a static-function. The +;;; routines themselves, however, take all of their arguments +;;; in registers (this will typically be one or two arguments, +;;; and is one of the lower bounds on the number of argument- +;;; passing registers), and thus don't need a call frame, which +;;; simplifies things for the normal call/return case. When it +;;; is neccessary for one of the assembly-functions to call a +;;; static-function it will construct the required call frame. +;;; Also, none of the assembly-routines return other than one +;;; value, which again simplifies the return path. +;;; -- AB, 2006/Feb/05. + (!def-vm-support-routine generate-call-sequence (name style vop) (ecase style ((:raw :none) @@ -20,7 +34,14 @@ `((note-this-location ,vop :call-site) (inst call (make-fixup ',name :assembly-routine)) (note-this-location ,vop :single-value-return) - (move esp-tn ebx-tn)) + (cond + ((member :cmov *backend-subfeatures*) + (inst cmov :c esp-tn ebx-tn)) + (t + (let ((single-value (gen-label))) + (inst jmp :nc single-value) + (move esp-tn ebx-tn) + (emit-label single-value))))) '((:save-p :compute-only)))))) (!def-vm-support-routine generate-return-sequence (style) @@ -28,9 +49,6 @@ (:raw `(inst ret)) (:full-call - `( - (inst pop eax-tn) - - (inst add eax-tn 2) - (inst jmp eax-tn))) + `((inst clc) + (inst ret))) (:none)))