- Feb 10, 2005
-
-
rtoy authored
connection is reset. Based on code from Scott Burson, cmucl-imp, 2005-01-31.
-
rtoy authored
accepted when computing namestrings. CLHS 19.2.2.2.3.1 says :unspecific components should not appear in the namestring. Make it so.
-
rtoy authored
unix-getgrnam and unix-getgrgid to select the buffer size. Apparently, some versions of Solaris won't work if the buffer is too small, even if the result would have fit. Bug pointed out by Damien Kick.
-
- Feb 09, 2005
- Feb 08, 2005
-
-
rtoy authored
there's already a scavenger hook printer.)
-
- Feb 07, 2005
-
-
rtoy authored
it so.
-
rtoy authored
-
rtoy authored
-
rtoy authored
-
rtoy authored
-
rtoy authored
o Remove some unused variables
-
rtoy authored
-
rtoy authored
o Make inet-recvfrom and friends available on Darwin again. * lisp/linux-stubs.S o Oops. Forgot to fix up #if with !defined(DARWIN) o Add recvfrom and friends to the stubs.
-
- Feb 06, 2005
-
-
rtoy authored
the 2005-02 snapshot to bootstrap.
-
rtoy authored
relatively straightforward port of the sparc version of linkage-tables. Some refinements are probably still needed, as well as some testing. Use boot-2005-02-ppc-linkage.lisp to bootstrap this change from the 2005-02 snapshot. * code/ppc-vm.lisp o Add appropriate FOREIGN-SYMBOL-ADDRESS-AUX and FIND-FOREIGN-SYMBOL functions for linkage-table. * compiler/generic/new-genesis.lisp o Basically do the same as the sparc port for linkage-tables. o need to extern-alien-name on the cold linkages since they C names depend on the backend conventions. * compiler/ppc/alloc.lisp o Load "undefined_tramp" appropriately for linkage-tables. * compiler/ppc/c-call.lisp o Define new vops (FOREIGN-SYMBOL-CODE-ADDRESS, FOREIGN-SYMBOL-DATA-ADDRESS) for linkage-tables so we can access correctly. * compiler/ppc/cell.lisp o Load "closure_tramp" appropriately for linkage-tables o Load "undefined_tramp" appropriately for linkage-tables * compiler/ppc/parms.lisp o Put the foreign linkage space start at the end of the static space to make it easier to bootstrap. (We need already mapped memory.) We can move this later. o Correct TARGET-FOREIGN-LINKAGE-ENTRY-SIZE. o Add new static-symbol *linkage-table-data* o While were at it, add SPARE-9 and SPARE-0 static symbols so we have 10 spares. * lisp/Config.ppc_darwin o Add -DLINKAGE_TABLE to CFLAGS/ASFLAGS if we have linkage-table support. * lisp/Darwin-os.c o Add os_dlsym to support linkage-tables. (This nees a little refactoring because we just copied the #defines for dlopen modes.) * lisp/os-common.c o The checking of the linkage tables that is done for sparc almost works for ppc, but not quite. Implement one for ppc. * lisp/ppc-arch.c o Add PPC version of arch_make_jump_entry, arch_make_linkage_entry, arch_linkage_entry. * lisp/ppc-assem.S o Add lazy_resolve_linkage to support linkage-tables. This needs some more work. o Add undefined_foreign_symbol_trap. This probably needs work, and definitely needs testing. * lisp/ppc-validate.h o Define the start of the linkage space and size.
-
rtoy authored
-
rtoy authored
-
cshapiro authored
demonstrably slower than extant compiler intrinsics or C runtime memset() implementations for blocks of memory greater than or equal to an x86 VM page.
-
- Feb 04, 2005
- Feb 03, 2005
-
-
rtoy authored
-
rtoy authored
work on Solaris 10. (Eventually, he gets a GC lossage). But setting -dynamic-space-size 256 works fine. The difference is that the default is 256 MB - 32 KB. So change the default to just 256 MB. We don't understand why the old default causes funny things to happen on Solaris 10.
-
- Feb 02, 2005
- Feb 01, 2005
-
-
rtoy authored
-
- Jan 31, 2005
-
-
rtoy authored
equal to *gc-trigger*, and that was causing GC not to happen in some cases on x86. He said changing > to >= in sub-gc fixes this problem.
-
- Jan 29, 2005
-
-
rtoy authored
when the length of the vector was a multiple of 32.
-
- Jan 27, 2005
-
-
rtoy authored
forwarded to cmucl-imp, 2005-01-17. Slightly modified the code therein. The functions are unix-recvfrom, unix-sendto, unix-shutdown, inet-recvfrom, inet-sendto, inet-shutdown.
-
rtoy authored
*last-bytes-in-use* and *gc-trigger* should be (unsigned-byte 32) instead fixnums. o Add simple docstring for gencgc-stats.
-
rtoy authored
Patch from Sverker Wiberg, cmucl-imp, 2005-01-18.
-
- Jan 25, 2005
-
-
rtoy authored
suppress it.
-
rtoy authored
case the user has set some printer vars to something too short. SLIME needs this. From Helmut Eller, cmucl-imp, 2005-01-24.
-
rtoy authored
statement.
-
rtoy authored
deftransforms. This causes a warning to be produced for (defun foo (f d) (declare (type (simple-array single-float (*)) f) (type (simple-array double-float (*)) d)) (setf (aref f 0) (aref d 0))) (from Lynn Quam, cmucl-imp 2004-03-30). Previously, no warning was produced and all code including the function return was deleted. Now a warning is produced and the code is not deleted. This is a workaround.
-
- Jan 13, 2005
-
-
fgilham authored
lisp.c into the correct <foo>-os.h files.
-
- Jan 07, 2005
-
-
rtoy authored
(defun fn-492 (r p1) (declare (optimize speed (safety 1)) (type (simple-array (signed-byte 8) nil) r) (type (integer * 22050378) p1)) (setf (aref r) (lognand (the (integer 19464371) p1) 2257)) (values)) confuses the compiler and causes (values) to be deleted, and also deletes the return from the function so we just run past the end into junk. I think it's caused by confusion in type derivation. I changed the defoptimizer for %aset so it returns the specialized element-type of the array instead of the new-value. This is a workaround, not a solution.
-
- Jan 06, 2005
-
-
rtoy authored
type of (logior positive-integer 0) to (integer 0 0). Same problem with logxor.
-
- Dec 24, 2004
-
-
rtoy authored
on Linux/x86, the Lisp signal handler for SIGSEGV overwrites the beginning of the control stack. For SIGSEGV we use an extra signal stack and when the signal isn't handled by the GC or by the stack overflow handler we call eventually call_into_lisp. call_into_lisp tests whether the current stack pointer points to the normal control stack. But the test fails because we use the extra signal stack, so call_into_lisp just sets the stack pointer to the beginning of the normal control stack. This is not much fun for debugging because the backtrace is truncated and it's also no longer possible to throw to the top-level-catcher because its frame was overwritten. I tried to fix that with the patch below. The idea is to switch back to the normal stack before calling the Lisp handler. The patch may not be very elegant but it is at least short :) .
-
rtoy authored
-