1
I Use This!
Inactive

Commits : Listings

Analyzed about 6 hours ago. based on code collected about 6 hours ago.
Sep 05, 2024 — Sep 05, 2025
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
0.pre7.106: merged NJF dolist-to-macrolet patch (sbcl-devel 2001-12-29) investigated why I can't resize SIMPLE-FUN, and scribbled various notes about what I found More... over 23 years ago
0.pre7.105: removed 10 obsolete entries in BUGS as per APD sbcl-devel 2001-12-29 More... over 23 years ago
0.pre7.104: 4-space tabs in C code More... over 23 years ago
0.pre7.103: rewrote LOOKUP-LOGIN-NAME to use getpwuid() instead of parsing "/etc/passwd" and then trying to speed up that fundamentally slow process by maintaining a fundamentally bogus cache of previous lookup results... ...deleted *UID-HASH-TABLE* ...deleted GET-GROUP-OR-USER-NAME ...deleted GET-GROUP-OR-USER-NAME-AUX ...defined uid_username() in wrap.c to encapsulate the C-level struct dereferencing ...factored the C-to-Lisp conversion logic out of POSIX-GETCWD, anticipating reusing it in LOOKUP-LOGIN-NAME ...rewrote LOOKUP-LOGIN-NAME to call uid_username(), and renamed it to UID-USERNAME More... over 23 years ago
0.pre7.102: changed some "#'(LAMBDA " stuff to "(LAMBDA " (changing only a few this time because when I changed more, things started breaking) fixed FIXME at head of primordial-extensions.lisp (since it's trivial now that EVAL-WHEN works) More... over 23 years ago
0.pre7.101: merged APD patches for readtable functions (2 patches, both on sbcl-devel 2001-12-24) More... over 23 years ago
0.pre7.100: deleted the rest of construct.lisp merged APD sbcl-devel 2001-12-21 partial fix and testcases for bug 134 (double backquotes) More... over 23 years ago
0.pre7.99: more dead construct.lisp code... ...CONSTRUCTOR-CODE-TYPE stuff ...all the GENERATOR-INTERNAL stuff in construct.lisp ...COMPUTE-INITARG-POSITIONS ...COMPUTE-CONSTANT-VECTOR (So probably the rest of construct.lisp is dead code too, but I'll try this partial deletion first.) More... over 23 years ago
0.pre7.98: belatedly 'cvs remove src/pcl/iterate.lisp' deleted dead code that I noticed when looking at NJF patch... ...DEFCONSTRUCTOR ...MAKE-CONSTRUCTOR ...LOAD-CONSTRUCTOR ...ENABLE-CONSTRUCTORS ...DISABLE-CONSTRUCTORS ...RESET-CONSTRUCTORS ...MAP-CONSTRUCTORS ...INSTALL-LAZY-CONSTRUCTOR-INSTALLER ...COMPUTE-CONSTRUCTOR-CODE ...SET-CONSTRUCTOR-CODE ...ADD-CONSTRUCTOR, REMOVE-CONSTRUCTOR, GET-CONSTRUCTOR ...CLASS-CONSTRUCTORS added note that more (all?) of construct.lisp might be dead More... over 23 years ago
0.pre7.95: (never checked into CVS separately, since I was travelling) gave up on fixing BACKTRACE function name nastiness for 0.7.0, wrote it up as bug 137 instead experimented with bootstrapping under CLISP (which still doesn't work, but at least fails at a new place now) More... over 23 years ago
0.pre7.94: more tweaking/tidying motivated by my feasibility study of making debug names be stored in a single place... ...rewrote DEBUG-INFO-FOR-COMPONENT to make it clear that it's working with LAMBDAs, not functions ...removed now-redundant GET-DEBUG-INFO-FUN-MAP in favor of SB!C::COMPILED-DEBUG-INFO-FUN-MAP More... over 23 years ago
0.pre7.93: debug name insanity, continued... ...added then backed out changes when I realized that (1) there are two distinct mechanisms for function names and (2) they're coupled by the FUN-DEBUG-FUN mechanism, bwahahahaha! ...tweaked and expanded comments (and whined on Advogato) to reflect my new knowledge of forbidden arcana of evil More... over 23 years ago
0.pre7.92: made function names (as returned by FUNCTION-LAMBDA-EXPRESSION and used by BACKTRACE) for DEFUNed functions mostly reasonable again, e.g. PRINT instead of "top level locall PRINT" ...made SETFable %FUN-NAME to encapsulate this ...renamed FUNCTION-DOC to %FUN-DOC for consistency ...got rid of NAMED-LAMBDA, since cold-load issues make it awkward to use it in DEFUN where I intended to use it, and there's no urgent other place to use it ...made %DEFUN use SETF %FUN-NAME (There are still function-name infelicities left, especially for closures where there's no good implementation of SETFable FUN-NAME until weak hash tables work, but at least most BACKTRACE entries look better now.) More... over 23 years ago
0.pre7.91: merged Nathan Froyd port of CMU CL FMAKUNBOUND fix (sbcl-devel 2001-12-18) More... over 23 years ago
0.pre7.90: changed publicly-visible DEF-FOO-style names to DEFINE-FOO: DEF-ALIEN-ROUTINE, DEF-ALIEN-TYPE, DEF-ALIEN-VARIABLE, DEF-SOURCE-CONTEXT (and a few other lexically-similar DEF-FOO-style names as well) defined deprecated wrappers using the old names defined DEPRECATION-WARNING to support this More... over 23 years ago
0.pre7.89: (gave in to the temptation to check in a version which had only been "rebuilt" with slam.sh, not full make.sh) changed default CHAR-NAME of unprintable ASCII characters not specified in the ANSI standard to #\Nul, #\Soh, etc. More... over 23 years ago
0.pre7.88: s/ir2-physenv-environment/ir2-physenv-closure/ changed most ~D in FORMAT strings to ~W changed debugger prompt to "5]", "5[2]", "5[3]", etc. More... over 23 years ago
0.pre7.87: merged flaky7_branch back into main branch More... over 23 years ago
0.pre7.86.flaky7.27: (Now DISASSEMBLE 'PRINT produces reasonable-looking output. In fact, AFAIK it's not flaky any more, so it should (finally!) be mergeable back into the main branch.) made GET-FUNCTION-SEGMENTS return a list (as its comments claim it does, and as its callers expect) even in the (NULL SEGMENTS) case renamed DEFUN REQUIRED-ARG to be consistent with all the previously-renamed MISSING-ARG calls More... over 23 years ago
0.pre7.86.flaky7.26: Duh. WITH-SIMPLE-RESTART doesn't restart its operation. So it's not a compiler bug, just the lack of an outer LOOP wrapper in TOPLEVEL-REPL, which has been blowing the system up. Gads. More... over 23 years ago
0.pre7.86.flaky7.25: (This passes regression tests, and seems to be a good thing in principle, but alas the generalization to include ENTRYs still doesn't fix the debugger restart problem.) generalized LAMBDA-CALLS-OR-CLOSES to include ENTRYs More... over 23 years ago
0.pre7.86.flaky7.24: I've come to suspect that the debugger/restart/QUIT problem has to do with the same closure/component bug I fixed above, except for closures over NLXs instead of over LAMBDA-VARs. So I'd like to generalize the LAMBDA-REFERS-TO-VARS fix to deal with NLXs as well. In preparation for that... ...merged LAMBDA-REFERS-TO-VARS and LAMBDA-CALLS into LAMBDA-CALLS-OR-CLOSES More... over 23 years ago
0.pre7.86.flaky7.23: about that debugger/restart/QUIT problem... ...added various new /SHOW-ish cruft ...rewrote HANDLER-BIND to be more nearly clearly compatible with ANSI HANDLER-BIND clause syntax The RESTART-NAME slot is constant and holds a symbol. More... almost 24 years ago
0.pre7.86.flaky7.22: removed various /SHOW-ish cruft about that debugger/restart/QUIT problem... ...revived SB-DI:FRAME-CATCHES enough that (BREAK), F 4, (SB-DI::FRAME-CATCHES SB-DEBUG::*CURRENT-FRAME*) shows %END-OF-THE-WORLD ...exported SB-VM:*CURRENT-CATCH-BLOCK* to support this More... almost 24 years ago
0.pre7.86.flaky7.21: removed REMOVEME stuff More... almost 24 years ago
0.pre7.86.flaky7.20: (This version bootstrapped successfully from 0.6.13, passed regression tests, served as its own bootstrap host, and passed regression tests again. But it still has debugger/signal/whatever problems, so that A doesn't work from the debugger prompt, and after it fails, (SB-EXT:QUIT) doesn't work either.) The failure in clocc-ansi-test was in the find-the-home-lambda part of the new code which updates LAMBDA-REFERS-TO-VAR in IR1 translation of SETQ. We try to find the home lambda by looking backwards through continuations, but in the (SETQ X 3) form in (SETQ X 2) (RETURN-FROM STOP) (SETQ X 3)) it doesn't work to look backwards. (To make a point which eluded me for a while, this isn't a bug in the way that continuations are set up, it's because the (SETQ X 3) form is orphaned by the way that control always jumps out through RETURN-FROM, so that the (SETQ X 3) form effectively has no home lambda.) So... ...redid CONTINUATION-HOME-LAMBDA in terms of CONTINUATION-HOME-LAMBDA-OR-NULL, and BLOCK-HOME-LAMBDA in terms of BLOCK-HOME-LAMBDA-OR-NULL ...made the update-LAMBDA-REFERS-TO-VAR code accept a NIL answer from CONTINUATION-HOME-LAMBDA-OR-NULL More... almost 24 years ago
0.pre7.86.flaky7.19: (bootstraps itself and gets through many regression tests, but dies in clocc-ansi-test :SECTION5-LEGACY-699) The obvious version of scavenging closure-over relationships still wanders into deleted lambdas, and when I stop it from wandering into deleted lambdas, the compiler fails in UNCONVERT-TAIL-CALLS when cross-compiling pprint.lisp. The problem is that a CONTINUATION-DEST is NIL when UNCONVERT-TAIL-CALLS is expecting it to be a NODE. So I looked at the description of DEST in DEFSTRUCT CONTINUATION, and looking at the way that the CONTINUATION-DEST is used in UNCONVERT-TAIL-CALLS and... ...made UNCONVERT-TAIL-CALLS handle null values of THIS-CALL (treating them as "can't possibly be one of the matches that I'm looking for") More... almost 24 years ago
0.pre7.86.flaky7.18: When I tried to scavenge closure-over relationships in an earlier failed version (never checked in) I got some weird failures related to scavenging into deleted lambdas. In anticipation of reencountering this problem soon, add some logic to the LAMBDA-CALLS scavenging to prevent it from happening there, and an assertion that it never does. More... almost 24 years ago
0.pre7.86.flaky7.17: (still works as well as before, still fails in pathnames.impure.lisp the same way as before, since all the changes are still only preparation for a real fix) removed various INLINEs in ir1util.lisp, to ease debugging and because I hope sometime next year to be doing some profiling on the compiler (so that if they really need to be inlined, I should soon find out) making FIND-INITIAL-DFO recognize closure dependencies... ...rearranged DFO-SCAVENGE-DEPENDENCY-GRAPH in preparation for walking through LAMBDA-REFERS-TO-VARS as well as LAMBDA-CALLS More... almost 24 years ago
0.pre7.86.flaky7.16: (still works as well as before, still fails in pathnames.impure.lisp the same way as before, since all the changes are still only preparation for a real fix) making FIND-INITIAL-DFO recognize closure dependencies, continued... ...In order to make the information conveniently available for DFO-SCAVENGE-DEPENDENCY-GRAPH, add a new slot LAMBDA-REFERS-TO-VARS, analogous to LAMBDA-CALLS. ...made IR1-CONVERT-VARIABLE and DEF-IR1-TRANSLATOR SETQ set LAMBDA-REFERS-TO-VARS as appropriate ...wrote untidy CONTINUATION-HOME-LAMBDA to support this ...tweaked CONTINUATION-STARTS-BLOCK and LINK-BLOCKS so that when IR1-CONVERT-IF uses them it sets up links early enough to let CONTINUATION-HOME-LAMBDA work ...made merge-LETs logic merge LAMBDA-REFERS-TO-VARS as it already merged LAMBDA-CALLS More... almost 24 years ago