Advanced RISC Machines Limited, ARM Cross Development tools.

Release 1.6

---------------------------------------------------------------------
Advanced RISC Machines Limited,
    Park End, Swaffham Bulbeck, Cambridge, CB5 0NA, England.
        Tel: +44 223 813000  Fax: +44 223 812800
---------------------------------------------------------------------

Copyright (C) 1993 Advanced RISC Machines Limited (ARM). All rights reserved.

This product is subject to continuous developments and improvements.  All
particulars of the product and its use contained in this product release are
given by ARM in good faith. However, all warranties implied or expressed,
including but not limited to implied warranties or merchantability or
fitness for purpose, are excluded.


Examples
========

Most of the programs in this directory are examples from the Cookbook.
You should refer to the Cookbook for details on how to compile and execute
these examples.

In addition, this directory contains two standard benchmarks:
   - Dhrystone (tests integer CPU performance)
   - Whetstone (tests floating-point performance)

'dhry' is a pre-compiled version of Dhrystone which has been compiled
with the correct flags to make it execute as fast as possible.  This
is a little-endian executable, and will only run on a little-endian
system.

To execute 'dhry' remotely on an ARM evaluation card, use:
   armwd -serial dhry                   - the windowed debugger
   armsd -serial dhry                   - the command-line debugger

To execute 'dhry' on the armulator, simply use:
   armwd dhry                           - the windowed debugger
   armsd dhry                           - the command-line debugger

To compile Dhrystone for yourself, use:
   armcc -w -DMSC_CLOCK -Otime -apcs 3/noswst dhry_1.c dhry_2.c -o mydhry

   -w                    disable warnings
   -DMSC_CLOCK           a macro definition needed by Dhrystone
   -Otime                execution time optimisations (rather than space)
   -apcs 3/noswst/nofp   /noswst => no software stack checking
                         /nofp   => no frame pointer

It is highly recommended that the noswst option should normally only if
there is hardware stack-overflow checking.  It is safe for Dhrystone
because the memory usage is well understood.  For instance,
memory will be silently corrupted if stack overflow occurs with the noswst
option enabled.

The nofp option frees up a register which normally stores the frame pointer
(resulting in slightly smaller and faster code), but makes debugging
difficult.  Note that this is option is not an apcs variant, but a simple
request to not use frame a frame pointer.  This option is not normally
recommended fro general use.

To compile Whetstone, use:
   armcc whetston.c
