Skip to content
Snippets Groups Projects
  1. Aug 21, 2003
  2. Aug 18, 2003
  3. Aug 12, 2003
    • gerd's avatar
      Lisp executable support. From Fred Gilham. · 297cb596
      gerd authored
      	* src/lisp/validate.c (image_dynamic_space_size): New variable.
      	(validate): Allocate spaces differently if the core is part
      	of the executable.
      
      	* src/lisp/lisp.c (initial_function_addr): New variable.
      	(main): Use it for the initial function if appropriate.
      297cb596
  4. Aug 04, 2003
  5. Jul 28, 2003
  6. Apr 28, 2003
    • cracauer's avatar
      · 257c3a31
      cracauer authored
      Don't damage argv[0] when startup code is invoced with absolute path.
      
      If we ever do a patch release this should be in.
      257c3a31
  7. Feb 25, 2003
  8. Feb 18, 2003
  9. Jan 29, 2003
    • toy's avatar
      o Adds support for searching for the lisp.core file based on the · a20170bc
      toy authored
        location of the lisp C binary, when CMUCLLIB is not given, and the
        core file is not specified.
      o Add support for a CMUCLCORE envvar, and a -lib option for setting
        the path for the library: search-list.
      o Added some spare static symbols for the sparc port so we don't have
        to cross-compile again for a while.
      
      See cmucl-imp archives for some more details.
      a20170bc
  10. Jan 23, 2003
    • toy's avatar
      From Eric Marsden: · f315d7f1
      toy authored
          fix typos in comments, signal more specific error types, remove
          some stale code, fix a few compiler warnings in the runtime.
      f315d7f1
  11. Aug 27, 2002
    • moore's avatar
      · bf84be07
      moore authored
      On x86 FreeBSD and Linux, change the way foreign symbol addresses are resolved.
      They now go through a table -- effectively a new space in the core file.
      Function references are resolved lazily, data references are resolved on startup
      and when a .so is loaded.  The end result is that cores can be dumped that
      contain references to symbols in shared libraries.  Also, the dependence of the core on addresses in the Lisp runtime is broken.
      
      The linkage table feature is controlled by :linkage-table and LINKAGE_TABLE in C
      runtime.  Several foreign symbols are now Lisp static symbols, so a cross
      compile is required whether or not the new stuff is used.  I've checked in
      boot4-cross-foreign-linkage.lisp that builds the compiler for linkage table; do whatever you usually do for the non-linkage table case:)  Seriously, lets start
      a discussion on standardizing "cross compilation," not to mention the general
      build procedure.
      bf84be07
  12. Jan 29, 2002
  13. Nov 29, 2001
  14. Feb 22, 2001
    • pw's avatar
      From Paul Foley · b221deeb
      pw authored
      A couple of typo corrections; fix main() in lisp.c (main returns int,
      not void!); stop ACCEPT-TCP-CONNECTION blocking other processes.
      b221deeb
  15. Oct 27, 2000
  16. Oct 24, 2000
  17. Oct 23, 2000
  18. Oct 16, 2000
  19. Sep 09, 1999
  20. Feb 20, 1999
    • pw's avatar
      Changes for Linux running on Alpha. · 25b808fb
      pw authored
      From: Julian Dolby <dolby@csag-226-8.UCSD.EDU>
      
        Enclosed below are diffs against the cvs repository as of Feb 12;
      aside from minor changes like using different include files
      (e.g. validate.h instead of x86-validate.h in Linux-os.c) and adding
      alpha-linux specifics unix-glibc2.lisp, there are two code changes.
      
       The first is to signal handling. I had to put the POSIX-SIGS
      ifdefs into places used by alpha but not by x86, and I ifdef'ed out
      most of the linux #define kludges for signals for alpha linux, since
      alpha linux uses OSF/1 signals rather than linux ones.
      
       The second is that the trick of or'ing 2 into the reg_ALLOC address
      to cause faults does not work on alpha linux since the kernel traps
      and handles the unaligned access; I did not find a way to change that
      kernel behavior, so I changed the code to or (1<<63) into the address
      to cause a seg fault, and then check, in the seg fault handler, to see
      if the high-order address bits are set.
      
       One change I made is to the memory layout (lisp/alpha-validate.h and
      compiler/alpha/parms.lisp); that change is not needed to make lisp run
      on alpha linux, but is there because I wanted more heap space.
      25b808fb
  21. Nov 21, 1997
  22. Nov 18, 1997
  23. Jan 21, 1997
  24. Nov 01, 1994
  25. Oct 25, 1994
  26. Oct 24, 1994
  27. Jul 05, 1994
  28. Mar 10, 1994
  29. Jan 28, 1994
  30. Apr 28, 1993
  31. Feb 09, 1993
  32. Jan 13, 1993
  33. Sep 08, 1992
  34. Jul 28, 1992
  35. May 25, 1992
  36. Apr 28, 1992
Loading