OVERVIEW

  There are 4 standard configurations of the VM:

               compiler options      intended for
  Release      -O3                   Deployment
  Debug        -O3 -g3               Debugging/profiling Java/Smalltalk
  Checked      -O0 -g3               Debugging the VM
  Profiling    -O3 -g3 -pg           Profiling the VM

  If you type 'make' or 'make arch=unc20' in the pal-vm directory then the
  first two will be built.  If you type 'make dev' or 'make arch=unc20 dev'
  then all 4 will be built.

HISTORICAL CONFIGURATIONS

  There are two historical configurations of the VM.  They may no longer
  work.  They use the test code in the src/VM/test subdirectory

  TestRelease  -O3 -g3               __TEST__
  TestDebug    -O0 -g3               __DEBUG__ __TEST__

  The test configurations don't run the actual VM, they just run the unit
  tests.

DEBUGGING GC BUGS

  Most of the builds (not Release) support constant gc.  It can be
  activated with the -constant-gc option or from the program:

  Java:
    ist.palcom.base.System.instance().enableConstantGC();
    ist.palcom.base.System.instance().disableConstantGC();

  Smalltalk:
    system enableConstantGC.
    system disableConstantGC.

  This will make the VM run very slowly, but will reveal GC mistakes
  (esp. forgetting to use handle classes, see UseOfC++.txt).  It is a
  good idea to run in gdb with a breakpoint in exit() when making use
  of this option.

TRACING BYTECODE EXECUTION

  The Debug and Checked VMs support a trace of all bytecodes executed.
  This can be activated using the -trace and -trace-after options or
  programmatically:

  Java:
    ist.palcom.base.System.instance().setTraceAfter(int bytecodes);

  Smalltalk:
    system setTraceAfter: anInteger.

  The meaning of the parameter is as follows:

    == 0   =>  Enable tracing of insns now
    >  0   =>  Enable tracing of insns after n bytecodes
    == -1  =>  Disable tracing of insns now
