- Jan 31, 2006
-
-
cvs2git authored
-
rtoy authored
scavenge_interrupt_context.
-
rtoy authored
registers, in case they're pointing into our heap and what they're pointing to has moved. lisp/Darwin-os.c: o Add support for getting the LR and CTR registers from the context. lisp/gencgc.c: o Handle LR and CTR registers when scavenging the interrupt context. lisp/ppc-lispregs.h: o Define reg_LR and reg_CTR appropriately.
-
- Jan 27, 2006
- Jan 25, 2006
-
-
rtoy authored
o Add *disassemble-flets* to control whether we disassemble flets/labels, in case there's an mistake in the implementation of this.
-
- Jan 24, 2006
-
-
rtoy authored
o Cleanup extra blank lines.
-
rtoy authored
-
rtoy authored
-
rtoy authored
-
rtoy authored
-
rtoy authored
-
rtoy authored
-
rtoy authored
-
rtoy authored
-
rtoy authored
o Add more detail to cross-platform cross-compile.
-
rtoy authored
o Add more detail to cross-platform cross-compile.
-
rtoy authored
o Add more detail to cross-platform cross-compile.
-
rtoy authored
o Add more detail to cross-platform cross-compile.
-
rtoy authored
-
rtoy authored
-
rtoy authored
-
- Jan 23, 2006
-
-
rtoy authored
with-fixed-allocation and number-dispatch.
-
rtoy authored
-
rtoy authored
-
rtoy authored
work and could probably be implemented better. With these changes (trace (labels foo bar)) will trace the labels function FOO in the function BAR. We only support encapsulate nil, here. No check is made for this. code/ntrace.lisp: o In TRACE-FDEFINITION, recognize a list as a valid function, and return the list as the value of TRACE-FDEFINITION. This seems wrong, but I'm not sure if there's a real fdefinition for it, or if we could create a fake one. code/debug-int.lisp: o In FUNCTION-DEBUG-FUNCTION, recognize a list as the name of a function, and find the corresponding compiled-debug-function and create and return the new compiled-debug-function.
-
rtoy authored
second element isn't a list (and thus doesn't really look like a flet/labels form).
-
- Jan 22, 2006
-
-
rtoy authored
-
- Jan 20, 2006
-
-
rtoy authored
o Save the args that are in registers before we create our stack frame. We were storing the args in our own stack frame, breaking the connection between these args and any args that were allocated on the stack. By doing this first, the register args and stack args are all contiguous as expected by the callback. o Create the stack frame appropriately with enough room to store our callee-saved registers. o We were not allocating enough space (4 args, not 3!) on the stack for funcall3 to save its args. I don't think funcall3 needs to, but this is safe. o Document the stack layout so the next person doesn't have to read the code to figure it out again.
-
- Jan 19, 2006
- Jan 18, 2006
-
-
rtoy authored
-
- Jan 17, 2006
-
-
rtoy authored
-
rtoy authored
non-adjustable arrays were adjustable, and vice versa.
-
rtoy authored
with [0.0, 0.0] to produce [-0.0,-0.0]. The correct answer is [-0.0,0.0]. This bug was reported by Mika Pihlajamaki, cmucl-imp, Dec 28, 2005. A simple test case is (defun foo2b () (* 0 (+ (if (< 1 1) 1 1) 3.14)))
-
- Jan 12, 2006
-
-
rtoy authored
-
- Jan 09, 2006
-
-
rtoy authored
the pretty-printer more robust. Bug and fix from Gareth McCaughan, cmucl-imp, 2006-01-09.
-
- Jan 05, 2006
-
-
rtoy authored
MULTIPLE-VALUE-BIND and than like WITH-OPEN-FILE and friends.
-
- Jan 04, 2006
-
-
rtoy authored
were not parsed correctly because the "T" in Tue was being treated as a date-time-divider. Don't allow a date-time-divider to be at the start of the string.
-
- Jan 03, 2006
-
-
rtoy authored
reference information for other conditions. This condition prints out a short message saying to look somewhere appropriate. o Use REFERENCE-CONDITION for the CONSTANT-MODIFIED condition. (Based on SBCL's REFERENCE-CONDITION.) This needs work to add more references.
-