bootfiles/20d/boot-2012-12-1.lisp::
  Add :alien-callback to *features*

bin/build.sh::
  Change bootstrap directory to 20d.

code/lispinit.lisp::
  * Register :alien-callback feature if enabled.
  * Heap overflow checking depends on gencgc, so register that only if
    both are enabled.

tools/comcom.lisp::
  Compile c-callback only if :alien-callback is a feature.

tools/worldcom.lisp:
  Compile alien-callback onlf if :alien-callback is a feature.

compiler/ppc/c-callback.lisp::
compiler/sparc/c-callback.lisp::
compiler/x86/c-callback.lisp::
 New file containing the callback code from c-call.lisp.

compiler/ppc/c-call.lisp::
compiler/sparc/c-call.lisp::
compiler/x86/c-call.lisp::
 Removed the callback code.

code/alien-callback.lisp::
 New file containing the alien callback code.

code/alieneval.lisp::
 Removed the alien callback code.

tools/comcom.lisp::
 Compile c-callback.lisp

tools/worldcom.lisp:
 Compile alien-callback.lisp.

entries with just the file path, removing the revision number, date,
author and state.  The actual information is now computed during
compilation and stored in the fasl itself.  (See ticket:48.)

sse2-packed-2008-11-12).

done in SBCL:

node.lisp:
  o Add new slots to cblock and component structures that are needed
    for loop analysis.

vop.lisp:
  o Enable the cloop structure.

loadcom.lisp:
  o Load loop

comcom.lisp:
  o Compile loop

No cross-compile needed.  When building, select the CLOBBER-IT restart
when asked.

	package COMMON-LISP which LISP uses, so that COMMON-LISP no longer
	has the non-ANSI nickname LISP.

	To bootstrap, use boot13.lisp as target:bootstrap.lisp with pmai's
	build scripts, and do a full compile.

	* src/bootfiles/18e/boot13.lisp: Change for all the package
	changes.

	* src/code/exports.lisp: New package common-lisp,
	which lisp uses.

	* src/tools/worldload.lisp:
	* src/tools/setup.lisp: Use cl-user instead of user.
	Use lisp:: instead of cl::.

	* src/tools/worldcom.lisp:
	* src/tools/snapshot-update.lisp:
	* src/tools/pclcom.lisp:
	* src/tools/mk-lisp:
	* src/tools/hemcom.lisp:
	* src/tools/config.lisp:
	* src/tools/comcom.lisp:
	* src/tools/clxcom.lisp:
	* src/tools/clmcom.lisp:
	* src/pcl/defsys.lisp:
	* src/motif/lisp/initial.lisp:
	* src/interface/initial.lisp:
	* src/hemlock/lispmode.lisp (setup-lisp-mode):
	Use cl-user instead of user.

	* src/code/save.lisp (assert-user-package):
	* src/code/print.lisp (%with-standard-...

The new XREF package exports function WHO-CALLS, WHO-REFERENCES, WHO-BINDS
and WHO-SETS. These return structures of type XREF-CONTEXT, which contain
the name of the referencing context, the file it was referenced from (or NIL
when compiling from the toplevel), and the source-position in that file.

Also change the names of lambda nodes in IR1 for macros and compiler-macros
to be lists of the form

   (:macro macro-name)
   (:compiler-macro macro-name)

instead of strings of the form "DEFMACRO MACRO-NAME".

Documentation has been added to the User's Manual.

This change shouldn't cause any bootstrapping problems when building.

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.

  * distributed binaries should no longer have OLD-xx package
    nicknames (for the VM and the compiler packages). These nicknames
    are set up by the build and cross-compile scripts, as needed.

the backend differers from the native backend - allows cross-compiling
form the x86 to the sparc which have differing byte orderings.

needs to be loaded and there is a better chance that the byte compiled
code will work.

Debug info is still selectively enhanced.

stuff for compiling each backend.

new-genesis.

stuff as we compile them.

compile time.

works with the new assembler.

Keep a bit more safety and debug-info when #-small.

want to support them anymore.

of float stuff refering to sap stuff.