1. 04 Nov, 2011 1 commit
  2. 30 Jun, 2006 1 commit
  3. 07 Nov, 2005 1 commit
  4. 12 Jan, 2004 1 commit
  5. 23 Oct, 2003 1 commit
    • toy's avatar
      o Add a few more comments · ddf5da3e
      toy authored
      o Make the features for the new backend a bit more up-to-date for the
        typical Sparc build that has linkage tables, stack-checking, and
  6. 20 Oct, 2003 1 commit
  7. 17 Oct, 2003 1 commit
  8. 29 Jan, 2003 1 commit
  9. 24 Oct, 2002 1 commit
  10. 27 Aug, 2002 1 commit
    • 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.