[Sbcl-devel] Re: [Sbcl-commits] CVS: sbcl/src/compiler/x86 nlx.lisp,1.13,1.14

[Christophe R. <cs...@ca...>]

Alexey Dejneka <ade...@us...> writes:

> Update of /cvsroot/sbcl/sbcl/src/compiler/x86
> In directory sc8-pr-cvs1:/tmp/cvs-serv22117/src/compiler/x86
> 
> Modified Files:
> 	nlx.lisp 
> Log Message:
> 0.7.13.15:
>         On X86 fixed amount of space for saving dynamic state
>         corresponding to removing of eval stack saving between
>         0.7.4.13 and 0.7.4.22. A similar patch probably should be
>         applied for other platforms.

>  (!def-vm-support-routine make-dynamic-state-tns ()
> -  (make-n-tns 3 *backend-t-primitive-type*))
> +  (make-n-tns 2 *backend-t-primitive-type*))

The similar patch has built without problems on SPARC/Solaris, so I
would say "yes, that seems likely".  I'll commit the sparc patch soon,
but I don't anticipate any problems with the other platforms.

How did you catch this?  Is there a way of making VOP* check that it's
being used consistently -- that is that the number of results matches
the length of the effective-&REST list, or is it not an error for them
not to match (and one of the elements is just being set to NIL)?

Cheers,

Christophe
-- 
http://www-jcsu.jesus.cam.ac.uk/~csr21/       +44 1223 510 299/+44 7729 383 757
(set-pprint-dispatch 'number (lambda (s o) (declare (special b)) (format s b)))
(defvar b "~&Just another Lisp hacker~%")    (pprint #36rJesusCollegeCambridge)