- Aug 11, 2012
-
-
Raymond Toy authored
* src/lisp/os.h * Move macros and definitions for FPU save/restore from here. * src/lisp/arch.h * Put architecture neutral stuff from os.h here. * src/lisp/ppc-arch.h * src/lisp/sparc-arch.h * src/lisp/x86-arch.h * Implement the FPU save/restore macros here for each supported architecture.
-
- Jul 05, 2012
-
-
Raymond Toy authored
-
- Nov 04, 2011
-
-
Raymond Toy authored
-
- Nov 12, 2008
-
-
rtoy authored
sse2-packed-2008-11-12).
-
- Nov 07, 2006
-
-
cshapiro authored
-
- Sep 15, 2005
-
-
rtoy authored
.indent.pro.
-
- Jul 07, 2004
-
-
rtoy authored
-
- Aug 27, 2002
-
-
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.
-
- Oct 27, 2000
-
-
dtc authored
-
- Oct 27, 1994
-
-
ram authored
-
- Oct 24, 1994
- Jan 13, 1993
-
-
cvs2git authored
-
- Sep 08, 1992
-
-
wlott authored
in case they contain useful information.
-
- Jul 28, 1992
-
-
wlott authored
-