1. 08 Oct, 2011 1 commit
  2. 01 Oct, 2011 3 commits
  3. 27 Sep, 2011 3 commits
  4. 25 Sep, 2011 3 commits
  5. 24 Sep, 2011 1 commit
    • Raymond Toy's avatar
      Fix Trac ticket:46. · 44a8f0c7
      Raymond Toy authored
      Make the size of all spaces configurable from the command line.
      
      code/commandline.lisp:
      o Define the switches so lisp doesn't complain.
      
      general-info/lisp.1:
      o Document new switches.
      
      general-info/release-20c.txt:
      o Update
      
      lisp/Darwin-os.c
      lisp/FreeBSD-os.c
      lisp/Linux-os.c
      lisp/NetBSD-os.c
      lisp/backtrace.c
      lisp/cgc.c
      lisp/gencgc.c
      lisp/os-common.c
      lisp/ppc-validate.h
      lisp/purify.c
      lisp/solaris-os.c
      lisp/sparc-arch.c
      lisp/sparc-validate.h
      lisp/x86-validate.h:
      lisp/validate.c
      o Basically rename CONTROL_STACK_SIZE, BINDING_STACK_SIZE,
        READ_ONLY_SPACE_SIZE, and STATIC_SPACE_SIZE to control_stack_size,
        binding_stack_size, read_only_space_size, and static_space_size,
        respectively.
      
      lisp/coreparse.c
      o Check the space size in the core file against the allocated size.
        If the allocated space is too small, print an error message and
        exit.
      
      lisp/globals.c
      o Define new variables for the allocated size of spaces.
      
      lisp/globals.h
      o Declare the new variables for the size of the spaces.
      
      lisp/lisp.c
      o Set the default values of the spaces.
      o Parse the new command-line flags and set the space sizes.
      
      lisp/sunos-os.c:
      o Added os_init0 (that we forgot last time).
      
      lisp/x86-assem.S:
      o Change $CONTROL_STACK_END to GNAME(control_stack_end) to get the
        correct end of the stack.
      44a8f0c7
  6. 21 Sep, 2011 3 commits
  7. 20 Sep, 2011 6 commits
  8. 19 Sep, 2011 1 commit
  9. 18 Sep, 2011 1 commit
  10. 03 Sep, 2011 3 commits
  11. 01 Sep, 2011 4 commits
    • rtoy's avatar
      Insert line breaks in the yellow-zone message. · 9babc9b1
      rtoy authored
      9babc9b1
    • rtoy's avatar
    • rtoy's avatar
      Add os_init0 to allow for some really early OS inits. · dafb9e03
      rtoy authored
      On Linux, os_init can re-exec lisp to set up the correct personality.
      Not normally a problem, but if any output happens before os_init is
      called, the output appears to happen twice.  So add os_init0 to do
      this early on, before any output.  This is a bit of a kludge.
      
      lisp/lisp.c:
      o Call os_init0 early in main.
      
      lisp/Linux-os.c:
      o Move the personality stuff from os_init to os_init0.
      
      lisp/Darwin-os.c:
      lisp/FreeBSD-os.c:
      lisp/NetBSD-os.c:
      lisp/OpenBSD-os.c:
      lisp/hpux-os.c:
      lisp/irix-os.c:
      lisp/mach-os.c:
      lisp/osf1-os.c:
      lisp/solaris-os.c:
      lisp/sunos-os.c:
      o Add dummy implementation of os_init0.  These OSes don't (currently)
        need anything special.
      
      lisp/os.h:
      o Declare os_init0.
      dafb9e03
    • rtoy's avatar
      Make the stack checking feature actually work on Darwin. Previously, · 4970f6a7
      rtoy authored
      stack overflows would crash lisp.
      
      Darwin-os.c:
      o Need to check for stack overflow in the sigbus handler.  (Without
        that, it's treated as a regular bus error.)
      o Add the rest of the infrastructure to handle the stack overflow.
      
      release-20c.txt:
      o Update
      4970f6a7
  12. 23 Aug, 2011 1 commit
  13. 21 Aug, 2011 2 commits
  14. 12 Jul, 2011 2 commits
  15. 29 Jun, 2011 2 commits
    • rtoy's avatar
      o Trac #43 fixed again. · 5b8db9f2
      rtoy authored
      o Add note about build-all.sh.
      5b8db9f2
    • rtoy's avatar
      Fix Trac #43 again. · 5e7baddc
      rtoy authored
      stream.lisp:
      o Remove the old code that was the first attempt at fixing issue #43.
        This was wrong.
      
      fd-stream.lisp:
      o Fix issue #43.  Even if we have a string-buffer, we need to take
        into account any octets in the in-buffer (if it exists) that have
        not been processed.  This happens if the in-buffer does not have
        enough octets at the end to form a complete character for the given
        encoding.
      o Some debugging prints added, but disabled.
      5e7baddc
  16. 28 Jun, 2011 1 commit
  17. 27 Jun, 2011 3 commits