* Get rid of the RCS Header stuff.  They're meaningless in git.
 * Add public domain comment to some of the files if the only comment
   was the RCS header.

Make the size of all spaces configurable from the command line.

code/commandline.lisp:
o Define the switches so lisp doesn't complain.

general-info/lisp.1:
o Document new switches.

general-info/release-20c.txt:
o Update

lisp/Darwin-os.c
lisp/FreeBSD-os.c
lisp/Linux-os.c
lisp/NetBSD-os.c
lisp/backtrace.c
lisp/cgc.c
lisp/gencgc.c
lisp/os-common.c
lisp/ppc-validate.h
lisp/purify.c
lisp/solaris-os.c
lisp/sparc-arch.c
lisp/sparc-validate.h
lisp/x86-validate.h:
lisp/validate.c
o Basically rename CONTROL_STACK_SIZE, BINDING_STACK_SIZE,
  READ_ONLY_SPACE_SIZE, and STATIC_SPACE_SIZE to control_stack_size,
  binding_stack_size, read_only_space_size, and static_space_size,
  respectively.

lisp/coreparse.c
o Check the space size in the core file against the allocated size.
  If the allocated space is too small, print an error message and
  exit.

lisp/globals.c
o Define new variables for the allocated size of spaces.

lisp/globals.h
o Declare the new variables for the size of the spaces.

lisp/lisp.c
o Set the default values of the spaces.
o Parse the new command-line flags and set the space sizes.

lisp/sunos-os.c:
o Added os_init0 (that we forgot last time).

lisp/x86-assem.S:
o Change $CONTROL_STACK_END to GNAME(control_stack_end) to get the
  correct end of the stack.

unicode-utf16-extfmt-2009-06-11.

  * Eliminate `printf' format string and the following arguments
    conflicts.

  * A variable may be used uninitialized.

  * A variable may be defined but not used.

<.  Print out an error message if the loop is exited with clean !=
static_free.

This prevents infinite loops that were sometimes seen on x86.
However, the infinite loops appear to be caused by some kind of
heap corruption.  This change just makes the corruption more
apparent.

The merge is from the tag "double-double-irrat-end".  The
double-double branch is now obsolete.

The code should build without double-double support (tested on sparc)
as well as build with double-double support (tested also on sparc).

fdefn-raw-addr-slot actually hold a tagged pointer instead of the raw
address.  Not sure if this is good or not, but making it like sparc
makes ppc a little easier.

Might need a cross-compile; the 2005-12-1-ppc cross-compile script
works fine.

assembly/ppc/arith.lisp:
o Static functions are now tagged, so need to adjust address before
  branching to them.

compiler/generic/new-genesis.lisp:
o Fill fdefn-raw-addr-slot with the tagged address instead of
  converting to untagged.

compiler/ppc/call.lisp:
o fdefn-raw-addr-slot is tagged, so need to adjust it before branching
  to function.

compiler/ppc/cell.lisp:
o No need to adjust function address before storing it in the
  fdefn-raw-addr-slot.

compiler/ppc/static-fn.lisp:
o Static functions are tagged, so need to adjust address before
  branching to them.

lisp/gc.c:
o Don't need scav_fdefn, because the fdefn is a tagged object now.

lisp/ppc-assem.S:
o Make undefined_tramp and closure_tramp be tagged instead of
  untagged.

lisp/purify.c
o RAW_ADDR_OFFSET is 0 now, like sparc.

.indent.pro.

the equivalent standard C mem{cpy,move,set} functions.

causing problems on x86/linux for some reason.  We should investigate
this later.

was mentioned by Dan Barlow on #lisp.

Change offset_vector back to an unsigned int* because it still has
32-bit elements on amd64. Eventually we will make this consistent with
internals.h. This creates a compiler warning, sigh.

* purify.c: fixup up fprintf warnings
* x86-validate.h:  LinkageSpaceStart is an unsigned, so cast it.

assigning pointers from integers.  From the scavenger_hook stuff.

integer.

  - detect overflow of static and read-only spaces during PURIFY. You get
    dumped into LDB.

  - fix a few signed/unsigned confusions in casts

    fix typos in comments, signal more specific error types, remove
    some stale code, fix a few compiler warnings in the runtime.

cases it's too small.  (Should we dynamically allocate this?)

  of the dynamic space. DYNAMIC_SPACE_SIZE now defines the maximum
  size, and when defined DEFAULT_DYNAMIC_SPACE_SIZE gives the default.

o Increase the maximum dynamic space size for Linux x86 to 1.625GB,
  with the default remaining at 512MB.

o Define the default dynamic space size for FreeBSD x86 to also be 512MB,
  with a maximum of 2GB.

because the necessary pages are zeroed by gc_free_heap.

dependent on pointer_filter_verbose.

of heap corruption and to try and handle return address on the stack.

Enhance new-genesis to save the code fixups for x86 code objects
allowing the code to be placed in the dynamic heap and thus garbage
collected by purify.

when there is no scavenger hook support (for CGC).

* Support for moving code objects on the x86 port. Needed by the GENCGC
version which places code objects in the dynamic space which are moved
to the read-only space by purify.

* Scavenger hook support; available with GENCGC.

* Conditional support for scavenging the read-only space when the
*scavenge-read-only-space* static symbol is defined. This is currently
used with the x86 GENCGC version so that new-genesis can place code
objects in the read-only space.

* Hooks to GENCGC.

types. Adds storage classes to the backend for these so they can be
stored in registers or on the stack without consing; new primitive
types etc. Also adds (simple-array (complex {single,double}-float))
array types to avoid consing and speed vectors operations.  All
these changes are conditional on the :complex-float feature. More work
is needed to exploit these changes: improving the type dispatch in the
various function; maybe compiler transforms or more VOPs to handle
common functions inline.

will place the instance in the static space but still move the
substructure lists and arrays to the RO space. This is needed for
compact-info environments which cache the last name in the instance
which needs to be scavenged, but the hash arrays can still be placed
in the RO space (the cache name was not being scavenge which could
cause a false hit if very unlucky). Shall uses this new option in
compiler/globaldb.lisp after people have had a chance to bootstrap in
this new support.

(signed-byte 16), (signed-byte 30), (signed-byte 32).  These patches
include the general support and the x86 backend support; more to
follow. The important changes are conditional on the :signed-array
feature so shouldn't affect the source without this feature. This work
has been driven by Raymond Toy.