Skip to content
Snippets Groups Projects
  1. Feb 04, 2005
  2. Feb 03, 2005
    • rtoy's avatar
      Martin Rydstrom reports that CMUCL with the default heap size doesn't · d0c874d1
      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.
      d0c874d1
  3. Jan 13, 2005
  4. Dec 24, 2004
    • rtoy's avatar
      From Helmut Eller, cmucl-imp, 2004-10-05: · 627128ba
      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  :) .
      627128ba
  5. Oct 20, 2004
    • rtoy's avatar
      Move the static space location for ppc/darwin. For some reason, OS X · 0b95c95e
      rtoy authored
      10.3 was putting some malloc'ed areas in the old (bigger) static
      space, which causes cmucl not to run.  Moving the space to 0x10000000
      makes it no longer overlap.  I don't understand the reason for this.
      OS X 10.2 doesn't have this problem.
      
      Use boot-2004-10-1-ppc.lisp to cross-compile this change.
      0b95c95e
  6. Oct 19, 2004
  7. Oct 16, 2004
  8. Oct 15, 2004
    • cwang's avatar
      typo · d89e9cd4
      cwang authored
      d89e9cd4
  9. Sep 24, 2004
  10. Sep 21, 2004
  11. Sep 14, 2004
  12. Sep 11, 2004
    • rtoy's avatar
      Port of SBCL's float-accuracy compilation policy. Intended to make · 571091c7
      rtoy authored
      double-float-epsilon actually be epsilon on x86.  No effect on other
      ports.
      
      The default precision is now 53-bit (double-float) instead of 64-bit
      (80-bit floats).  However, to preserve C expectations, all calls to C
      have the precision set to 64-bit.  This slows down calls to C, but we
      try to make syscalls and such fast by not changing precision for the
      call.
      
      By default ext:float-accuracy is 3.
      
      Use boot7.lisp to bootstrap.
      571091c7
  13. Aug 17, 2004
  14. Aug 06, 2004
  15. Aug 04, 2004
  16. Aug 02, 2004
  17. Jul 30, 2004
  18. Jul 29, 2004
  19. Jul 27, 2004
  20. Jul 25, 2004
  21. Jul 24, 2004
  22. Jul 20, 2004
  23. Jul 15, 2004
  24. Jul 14, 2004
  25. Jul 13, 2004
    • pmai's avatar
      First merge of the C side of the OS X/Darwin port. Besides adding Darwin · eb44537a
      pmai authored
      versions of all the required things, this commit separates the
      interrupt handler proper (now interrupt_handle_now_handler) from the
      actual work-horse (interrupt_handle_now), which is now only ever called
      from the two interrupt handlers, interrupt_handle_now_handler and
      maybe_now_maybe_later.  This follows similar changes in SBCL, and is in
      fact needed in order to properly use sigreturn in signal handlers, as
      required to work around a problem with the G5.
      eb44537a
  26. Jul 12, 2004
  27. Jul 08, 2004
Loading