Custom Query (1030 matches)

We don't compile asdf.lisp during rebuild-ccl, because it had undesirable compile-time side-effects. See r14804, ticket:773, and ticket:765.

ASDF 3's behavior is supposed to be simplified, so it's probably worth taking a look at this again. It may now be harmless to compile asdf.lisp Or, alternately, we could add a stage to rebuild-ccl that compiles an additional set of files (including asdf.lisp) in the newly-build lisp (via run-program). This would prevent compile-time side-effects from messing up the image.

? (compile nil '(lambda () (typep nil '(or none-such null)))) 
> Error: Unknown type specifier: NONE-SUCH 
> While executing: CCL::%%TYPEP, in process listener(1). 
> Type :POP to abort, :R for a list of available restarts. 
> Type :? for other options. 
1 >  

I'm working on a fix, just entering the bug for the record.

The following transcript suggests the presence of a new bug in the CCL compiler in the vicinity of subtypep. Probably part of a disagreement about when (values ...) can be used in a type expression. Something like this just broke an ACL2 rebuild that didn't break yesterday.

% ccl -n
Welcome to Clozure Common Lisp Version 1.4-dev-r12509M-trunk  (LinuxX8664)!
? (defvar x)
X
? (defvar y)
Y
? (defun foo () x)
FOO
? (defun bar () y)
BAR
? (proclaim '(ftype (function () (values t)) foo bar))
NIL
? (defun fap () (- (foo) (bar)))
> Error: VALUES type illegal in this context:
>          (VALUES T)
> While executing: (:INTERNAL CCL::NX1-COMPILE-LAMBDA), in process listener(1).
> Type :GO to continue, :POP to abort, :R for a list of available restarts.
> If continued: continue compilation ignoring this form
> Type :? for other options.
1 >