Skip to content
Snippets Groups Projects
  1. Oct 30, 2001
    • pmai's avatar
      This change causes archives passed as a file argument to load-foreign · 184c40f3
      pmai authored
      to be loaded in-full, which is the only useful behaviour when trying
      to link with static libraries.  Currently this change only corrects
      the situation for Linux and Solaris, since I don't know the relevant
      flags for other platforms, and/or don't have access to machines for
      testing.
      184c40f3
  2. May 14, 2001
  3. Jan 05, 2001
  4. Sep 27, 2000
  5. Apr 19, 2000
  6. Aug 30, 1998
    • dtc's avatar
      Revise the address map to better utilise the address space, allowing · 0d71a1cd
      dtc authored
      larger heaps and stacks:
      
      * There is now the potential for up to 2.75GB dynamic space on
      FreeBSD, and 1.75GB on linux.  Since GENCGC statically allocates page
      tables the default size is set at just 1GB.
      
      * The Read-only and Static spaces have been increased to 256MB
      allowing larger heaps to be purified. The Read-only and Static spaces
      are in the same locations for both the FreeBSD and Linux ports to
      avoid unnecessary binary incompatibility.
      
      * The Control stack and Binking stack now have room for upto 128MB,
      supporting deeply nested algorithms, and potentially giving room for
      subdivision for thread stacks.
      
      * There is a reserve for the FreeBSD static libraries in the event
      that the FreeBSD lisp binary is dynamically linked, and the foreign
      segment size for FreeBSD is now 32MB, up from just 4MB.
      
      * There is now significantly more room for C allocated memory, roughly
      128M on Linux and 224M on FreeBSD.
      0d71a1cd
  7. May 01, 1998
  8. Nov 15, 1997
  9. Nov 11, 1997
  10. Oct 25, 1997
    • pw's avatar
      From: Timothy Miller <tsm@cs.brown.edu> · 9a08b1c8
      pw authored
      Ok, here are the updated patches to make the same cmucl lisp.core work
      across OS versions under irix, still by making tzname resolved at runtime
      (on irix only).
      9a08b1c8
  11. Aug 23, 1997
    • pw's avatar
      I just finished making load-foreign work on SGIs, along with fixing calling of · efd9aa3b
      pw authored
      foreign functions taking floating-point arguments after integer arguments but
      before the fourth argument (more or less; mips has unusual C calling
      conventions), and making cmucl work on IRIX 6.2 on the Onyx (where the system
      page size has changed). I've included the patches below, along with some
      discussion of the changes and a couple of problems with cmucl's interaction with
      dynamic loading. Also, there's a misc change to make ioctls work (I'm not sure
      for what version the released code worked, but it doesn't work on anything I
      have). The patches do not fix the R10000; cmucl continues to not work on it (O2
      and Octane).
      
      The fixes make cmucl on the sgi use shared libraries so it can use dlopen et al
      in load-foreign; this is based on the solaris implementation. The problem with
      this is that the addresses of foreign variables are included directly in the
      dumped lisp image (without relocation on loading), which might result in a
      problem if cmucl is run with newer shared libraries than those it was compiled
      and dumped with. As far as I can tell, for the SGI at least, this does not
      affect function calls because the addresses used (and included in the dumped
      image) are those of stub routines that jump to the actual routines, thus are
      located in the executable proper rather than in the shared libraries, and so
      shouldn't be changed by a new version of the shared library.
      
      Unfortunately, this is not the case for global variables. Fortunately, there
      appear to only be two foreign variables used by cmucl in any of its system code
      winding up in the dumped image: errno and tzname. Apparently, Solaris relocates
      data references in dsos to match the program, while IRIX relocates data
      references in the program to match the dso. Thus, on Solaris, you don't need to
      do anything special for cmucl to work with a newer runtime libc, but on IRIX it
      gets the wrong value of errno and tzname. Unfortunately, the address of errno is
      different between irix 6.2, 6.3, and 6.4 (all of which we have to have because
      SGI doesn't have a single cross-platform OS version yet), which would require a
      different lisp.core for each machine (you just need to run mk-lisp, not
      recompile) if it weren't for the hack below. But fortunately again, a lisp
      compiled for one version seems to be able to run on another version well enough
      to generate the new lisp.core (presumably the worst that would happen is that
      error messages could be confusing). It would be really nice to avoid this
      problem. Perhaps some kind of relocation table could be added to the dumped
      image format? I don't know enough about the system to know how possible or
      ridiculous that suggestion is, unfortunately. Is the Solaris behavior guaranteed
      to be the same in future releases? If not, or if any other platforms have the
      irix behavior, this might become a more general problem. In the meantime, we use
      a hack: we *define* errno in undefineds.c rather than just referencing it; this
      results in warnings from the linker, but it resolves the conflict in favor of
      the definition in the program, relocating libc to match, thus fixing this
      problem for errno. The other global variables, tzname et al, can't be fixed this
      way as easily because they're listed as weak symbols, essentially aliases for
      the real symbol, so redefining them wouldn't cause libc to reference the new
      version. Thus, as long as you don't use tzname, there's no problem right now
      (although there may be if any other library global variables are used in cmucl
      in the future). The definition of tzname is in a progn preceeded by a comment
      which says not to use it, so hopefully it's not in fact used and therefore not a
      problem.
      
      
      These patches have been tested on an R5000 O2 running irix 6.3 and a dual R4400
      Onyx running irix 6.2. A previous version of these patches (for 17f) was tested
      on the onyx when it was running 5.3 (I think, maybe 5.2). The patches here are
      from the main branch of the CVS tar as of August 13. Incidentally, it was quite
      painful figuring out how to compile and bootstrap the current sources under the
      distributed irix 18a binary, even without trying :new-random or :signed-array
      (which I haven't tried to do yet); it might be nice to put a newer binary up...
      efd9aa3b
  12. Aug 05, 1997
  13. May 05, 1997
  14. Jan 18, 1997
  15. Feb 16, 1995
  16. Nov 04, 1994
  17. Oct 31, 1994
  18. Oct 19, 1994
  19. Oct 01, 1994
  20. Sep 29, 1994
  21. Jul 05, 1993
  22. Feb 07, 1993
  23. Jan 13, 1993
  24. Jul 17, 1992
  25. Mar 04, 1992
  26. Mar 02, 1992
  27. Feb 26, 1992
  28. Feb 14, 1992
  29. Aug 30, 1991
  30. Feb 08, 1991
  31. Feb 01, 1991
  32. Jan 31, 1991
  33. Jun 15, 1990
  34. May 30, 1990
  35. Mar 05, 1990
  36. Feb 06, 1990
Loading