1.0.48.35: SB-EXT:GC-LOGFILE GENCGC only. (SETF SB-EXT:GC-LOGFILE) to a pathname starts logging before/after generation statistics there. Doing the same with NIL stops logging.
1.0.48.34: MAKE-ALIEN-STRING An easy way to copy lisp strings to malloc'ed memory. I can't believe we didn't have this before. ...just seems insane. I keep expecting to find a nice way to do this squirreled away somewhere in SB-ALIEN. Here's hoping I won't embarrass myself by finding one. Also fix the OAOOM in MAKE-ALIEN and FREE-ALIEN documentation: make the docstrings the canonical versions, and include them in the manual.
1.0.48.33: --script bits and pieces * Leaving out the script name means to read the script from standard input. In this case the shebang line is _not_ handle -- simply because I ran out steam. (Our shebang line processing assumes a seekable stream.) * Stream errors on standard streams cause scripts to exit silently. lp#770222. * Scripts no longer us *TTY* for *TERMINAL-IO*, but make up a two-way stream from *STDIN* and *STDOUT*. Similarly for *DEBUG-IO* but using *STDERR*. This means that backtraces from errors are now neatly captured in the standard error stream.
1.0.48.31: WITH-LOCKED-SYSTEM-TABLE Instead of disabling interrupts in user code that needs WITH-LOCKED-HASH-TABLE, have a separate WITH-LOCKED-SYSTEM-TABLE that does so. Use it instead of WITH-LOCKED-HASH-TABLE for all internals.
1.0.48.30: adjust DOCUMENTATION and SB-INTROSPECT Now that non-standard special operators can also have macro definitions for consumption by code walkers, make sure we get the special operator source location and documentation instead of the ones for the dummy macro.
1.0.48.29: better end-of-the-world handling * Implicit QUIT. * Make sure we have %END-OF-THE-WORLD visible while doing cleanups. * Handle errors from cleanups. * Disable interrupts in places where the environment might now be up to handling them yet/anymore. * If user calls QUIT, and exit hooks run without serious trouble, report the exit status requested even if there is trouble later flushing streams, etc. * Also make SAVE-LISP-AND-DIE signal an error if SAVE returns. (When there is eg. a file with the desired name but insufficient permissions.)
1.0.48.28: make TRULY-THE macroexpandable
lp#771673
* MACRO-FUNCTION no longer checks :FUNCTION :KIND, allowing us to have
special operators with macro-expansions in the first place.
* Add %MACROEXPAND and %MACROEXPAND which are careful not to expand special
forms, and use them in place of SB!XC:MACROEXPAND.
* Set the :FUNCTION :MACRO-FUNCTION into an expander that just converts
it to THE. This only happens when someone explicitly calls MACROEXPAND
or uses MACRO-FUNCTION directly -- never in the compiler.
* Also add a SETF-expander.
1.0.48.27: sb-posix: make syscall errors report the failing function Also add a declaim for the SYSCALL-ERROR ftype so the failing function will not be tail-merged is SYSCALL-ERROR appears in tail position.
1.0.48.25: automatic &rest to &more conversion
lp#504575
Automatically convert
(values-list rest-arg)
to
(%more-arg-values more-context 0 more-count)
when possible, making functions such as
(defun foo (f1 f2 &rest args)
(apply f1 args)
(apply f2 args))
non-consing.
The conversion is done iff:
* The rest arg is never assigned to.
* The rest arg only appears in VALUES-LIST (incl. APPLY)
calls.
* Those calls are all in either the same lambda that
allocates the rest-list, or one that has been declared
dynamic extent. (Conservative guess re. escaping.)
The way this works is as follows:
1. When we convert a lambda with a non-ignored &rest argument, as add
more-context and more-count arguments to the function, and
stick their lambda-vars into arg-info-default of the &rest arg.
2. When we source-transform a values-list form, we check if its argument is
a &rest argument for which context and count are available. If so, we
source-transform into
(%values-list-or-context list context count)
3. When we are optimizing, a deftransform fires for the form above. It
checks if all the necessary conditions hold and converts into either
%more-arg-values or values-list.
The reason for this roundabout way of doing things lies in locall analysis:
unless the extra context and count argument are used nontrivially when it
runs, they get deleted -- and we don't know if we want them or not until the
entire function has been converted. Absent a convenient pass between
conversion and locall analysis, we must therefore do things in two stages.
1.0.48.24: fix performance / type derivation regression from 1.0.48.14 Since global/special variables are now always converted using SYMBOL-VALUE / SYMBOL-GLOBAL-VALUE, we temporarily lost type information for them. Remedy this by adding a DERIVE-TYPE optimizer for both.
1.0.48.23: faster with-arguments CALL-NEXT-METHOD * Make the correctness-checking code for changed arguments in safe code check required arguments pairwise with EQL first -- if they match, the applicable methods must be the same and we can elide the expensive computation. This makes things like (apply #'call-next-method r1 r2 :foo foo rest) not suck horribly in safe code. Could still be better, but this much was quick and easy. * Make the &REST list in CALL-NEXT-METHOD dynamic-extent. This helps normal safety code as well.
1.0.48.21: explicitly indefinite-extent leaves, safer dynamic-extent &REST Change LEAF-DYNAMIC-EXTENT to LEAF-EXTENT. Setting it to :INDEFINITE stops dynamic-extent propagation through the leaf. Use this in CONVERT-MORE-CALL / CONVERT-HAIRY-FUN-ENTRY by proclaiming the variables in the open-coded &REST list as having indefinite-extent. The upshot is that dynamic-extent &REST will only stack allocate the spine of the rest list, making it easier and safer to use. Document this in the manual and attach appropriate caveats re. portability.
1.0.48.19: another go at fixing the win32 build Roll back the last attempt, that was not only incomplete, but somewhat ill adviced. Instead, put in :UNKNOWN as FD-STREAM-FD-TYPE if we need to serve events, and :REGULAR otherwise.