Parent Directory | Revision Log
|Links to HEAD:||(view) (annotate)|
|Links to unicode-utf16-extfmt-2009-03-27:||(view) (annotate)|
Merge changes from utf16 branch to update to snapshot 2008-12.
Sync to snapshot 2008-11. But we didn't sync code/extfmts.lisp or iso8859-1.lisp and utf-8.lisp. (I don't think we want those changes, yet.)
Add -DUNICODE to flags if FEAUTURE_UNICODE is set.
Remove X11 from the search path for include files.
Compile e_rem_pio2.c with -fno-strict-aliasing.
Minor changes to support the latest betas of FreeBSD 7. * Update the Config file to detect the GCC version at build time and use -iquote instead of -I- if we are not using GCC 2 or 3. This silences the unsilenceable deprecation message emitted by GCC 4. * Check the FreeBSD version at compile time and switch the protection violation signal to SIGSEGV if we are on a version of FreeBSD 7 that will deliver a SIGSEGV instead of a SIGBUS for access errors. * Install sigbus_handler to handle whatever UNIX signal the macro PROTECTION_VIOLATION_SIGNAL expands to. Get rid of the useless sigsegv_handler. Add the PROTECTION_VIOLATION_CODE macro so we do not have to conditionalize the check that guards the write barrier code.
Revert Config.FreeBSD_gencgc because executable feature now done correctly.
featureized version of executable stuff
Compile in e_rem_pio2.c and k_rem_pio2.c. Someone running FreeBSD and NetBSD should verify this is correct.
Remove all references to non-existent directory "../../p86/lisp".
Lisp executable support. From Fred Gilham.
Tim Moore says linux-stubs is not needed with LINKAGE-TABLE so remove it and make linking happy.
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.
Support for dynamic loading in FreeBSD 4.0 and later. This involves moving the static space up, so a cross-compile is required to bootstrap these changes.
o Cleanup of the Config files.
Cleanup the source paths.
Fix the spelling of undefineds.c, noticed by Paul.
Conservative generational garbage collection for the x86 port.
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, select a symbolic revision name using the selection box, or choose 'Use Text Field' and enter a numeric revision.
|Powered by ViewVC 1.1.5|