* Have SB-COVER use md5sums of filenames for URLs. * Have the test of SB-MD5:MD5SUM-FILE take the md5sum of a fresh empty file, rather /dev/null or NUL, so that the test is independent of any other limitations in CL:OPEN on Windows.
* Test file didn't compile under #-gencgc builds.
* Preclude a buffer overflow (though one that cannot occur at present, given the single caller of this routine). Contributed by Alex Plotnick.
* Thanks to Lutz Euler. (No 32 bit variant of the instruction in 64-bit mode.)
…CLASS * Just pass source-location / definition-source along the necessary code-paths -- all the required infra is already in place. * Also get the source locations for PCL itself: it would be embarassing not to have the source location for SB-PCL::DEFINITION-SOURCE. :)
…lly) * Thanks to David Smith.
…TRUCT * Thanks to David Smith.
* Rewrite SPLIT-DECLARATIONS to use two (short) constant lists and INFO instead of *VAR-DECLARATIONS-WITH|WITHOUT-ARG*. * Test-case for #402. * While at it, replace the *VAR-DECLARATIONS* from walker as well, replacing it with WALKED-VAR-DECLARATION-P, and make VAR-DECLARATION use a compiler-macro to check for bogus-declarations when possible. (All our whopping 3 calls to it.) * Bug #413 was fixed in 1.0.13, remove it from BUGS. * Whitespace.
* Windows is not happy about files with open handles dancing around. This should one of the SB-COVER problems on Windows, and is arguably better for posixoid platforms as well. * SET-CLOSED-FLAME immediately after closing the fd, since that is in a very real sense the boundary after which doing stream operations is going to lose. * Windows additions to .gitignore.
* Most likely due to changes in debug instrumentation. :/ Add to regression suite, in case it comes back.
* Pre 220.127.116.11 version ended up calling %FLOOR, and all was well. Now we need to check explicitly for zero. Reported by Michael Weber.
* Used to signal an error -- report lack of samples, and return NIL instead. Reported by Andy Hefner on sbcl-devel 2008-01-06.
* AMOP requirement, reported by Levente Meszaros on sbcl-devel 2007-04-20. * New condition class for convenience: SB-INT:SIMPLE-REFERENCE-ERROR.
* Unchecked RETURN reported by Kevin Reid.
* Use NAME-LAMBDALIKE to construct the debug-name if :NAME is NIL. * Also make sure the SOURCE-NAME is not NIL, but .ANONYMOUS. if none is provided. * Correct handling of &OPTIONAL-PROCESSOR debug-names: the debug-name keyword is provided by the callers, so we cannot default it as part of the keyword parsing (in case it is NIL), additionally, even if we have a debug-name already, we still want to make up an &OPTIONAL-PROCESSOR debug-name. * Ensure (and strategically AVER) that we have a non-null debug-name for things which are .ANONYMOUS. -- by making up one using NAME-LAMBDALIKE if nothing else. * AVER that the second argument of DEBUG-NAME is not NIL. * Test that (COMPILE NIL '(LAMBDA ...)) doesn't make function which backtrace as NIL anymore.
* Not a performance consideration, but rather part of tidying up code paths that lead DEBUG-NAME to be called with NIL as the second argument (in IR1-TOPLEVEL the form becomes part of the TOP-LEVEL-FORM debug-name.)
* Instead of LVAR-FUN-NAME, use new LVAR-FUN-DEBUG-NAME, which works even for multiply-used lvars, by returning the list of names instead of just NIL.
* Copying them from the original leaf before converting the replacement function.
* Make *DEBUG-NAME-LEVEL* behave more like *PRINT-LEVEL*, and add *DEBUG-NAME-LENGTH*. Now, instead of the old (VARARG-ENTRY (LAMBDA (&OPTIONAL ("#<...>" . "#<...>") . "<...>"))) we get (VARARG-ENTRY (LAMBDA (&OPTIONAL (FOO *BAR*) (QUUX *ZOT*))) which is a lot more useful. * Use slightly magical debug name markers that print as # and ... instead of strings when abbreviating names.
…cates * AKA less mysterious (LAMBDA (OBJECT)) potential in statistical profiling &co. (No, I haven't been overly troubled by such functions, but since it is easy to give these ones names, we just as well may.)
...2008! Shell portability issues! AAARGH! (Ok, slightly embarrassed as well.)
* 18.104.22.168 took care of the (SAP= CURRENT END) aver failure, but other issues remain.
* Texinfo, not DocBook since late 2004. :) We're fast on things like this. * HTML available for download, not part of the normal binary distribution. * Mention BUGS. * PURIFY doesn't happen on x86 Darwins, and I've never had to touch the limits on PPC either -- so delete that bit.
* I'm tired of typing the mantra, and it's probably good to make it easy for users too to run SBCL before installation. * Add to binary tarball, and mention in INSTALL.
...adapted from sbcl-devel.
* sb-aclrepl: Display single-floats in IEEE-756 format for 64-bit platforms for consistency with 32-bit platforms.
* Instead of *MAX-EVENT-(U)SEC* use *PERIODIC-POLLING-PERIOD*. * After polling, if there is any more waiting left to do, call SUB-SERVE-EVENT again. (The old implementation did not do this, but this seems right to me.) * Export the API, and mark as EXPERIMENTAL. Unadvertised in the docs or NEWS for now -- but the docstrings should be clear enough. Waiting for happiness report from CLG folks before publishing this.
* sb-aclrepl: Fix inspection of single-floats on 64-bit platforms which are now unboxed data.
* Reported by Elliot Slaughter.
* logged a bug * searched for sbcl-devel references and added notes about the need to subscribe (since the mailman bounce message is particularly unhelpful, and I periodically get mail from frustrated would-be posters) * fixed a few typoes * revised a few passages, and completely gave up on trying to summarize SBCL performance in a paragraph in the man page
* There are two cases where we used to fail our AVER (SAP= CURRENT END) in MAP-ALLOCATED-OBJECTS: -- If we had constructed an unlucky bogus object or few during our heap traversal, we might be just sufficiently out of synch to overstep it. -- If we allocated new objects past the original END during heap traversal and, and the mapped over them. * Fix the last case always: before calling the provided function, check that the object ends before END. * Fix the second case for fastidious callers (and add an optional argument so callers can inform us about their fastidiousness) by using MAKE-LISP-OBJ instead of %MAKE-LISP-OBJ. ROOM still uses the old version, since the careful approach is too slow, and even the slow path uses %MAKE-LISP-OBJ in the less-error-prone cases. ...so not quite perfect yet.
* Also document *INIT-HOOKS* and *SAVE-HOOKS*. * Trailing whitespace cleanup in start-stop.texinfo.