old-cross-binutils/sim/mips
Jackie Smith Cashion f24b7b69ee Mon Sep 16 11:38:16 1996 James G. Smith <jsmith@cygnus.co.uk>
* interp.c (sim_monitor): Improved monitor printf
 	simulation. Tidied up simulator warnings, and added "--log" option
 	for directing warning message output.
	* gencode.c: Use sim_warning() rather than WARNING macro.
1996-09-16 10:47:20 +00:00
..
.Sanitize Added. 1996-06-26 10:08:42 +00:00
ChangeLog Mon Sep 16 11:38:16 1996 James G. Smith <jsmith@cygnus.co.uk> 1996-09-16 10:47:20 +00:00
configure * configure.in: Add calls to AC_CONFIG_HEADER, AC_CHECK_HEADERS, 1996-06-03 15:58:45 +00:00
configure.in * Makefile.in (bindir, libdir, datadir, mandir, infodir, includedir, 1996-06-26 03:26:09 +00:00
gencode.c Mon Sep 16 11:38:16 1996 James G. Smith <jsmith@cygnus.co.uk> 1996-09-16 10:47:20 +00:00
interp.c Mon Sep 16 11:38:16 1996 James G. Smith <jsmith@cygnus.co.uk> 1996-09-16 10:47:20 +00:00
Makefile.in * configure.in: Add calls to AC_CONFIG_HEADER, AC_CHECK_HEADERS, 1996-06-03 15:58:45 +00:00
README.Cygnus Initial check-in of the MIPS simulator. Work still needs to be done on 1995-11-08 15:44:38 +00:00
support.h * gencode.c (process_instructions): Generate word64 and uword64 1996-07-18 01:21:16 +00:00

> README.Cygnus
-------------------------------------------------------------------------------

The following are the main reasons for constructing the simulator as a
generator:

1) Avoid large fixed decode source file, with lots of #ifs controlling
   the compilation. i.e. keep the source cleaner, smaller and easier
   to parse.

2) Allow optimum code to be created, without run-time checks on
   instruction types. Ensure that the simulator engine only includes
   code for the architecture being targetted. e.g. This avoids
   run-time checks on ISA conformance, aswell as increasing
   throughput.

3) Allow updates to the instruction sets to be added quickly. Having a
   table means that the information is together, and is easier to
   manipulate. Having the table generate the engine, rather than the
   run-time parse the table gives higher performance at simulation
   time.

4) Keep all the similar simulation code together. i.e. have a single
   place where, for example, the addition code is held. This ensures that
   updates to the simulation are not spread over a large flat source
   file maintained by the developer.

-------------------------------------------------------------------------------

To keep the simulator simple (and to avoid the slight chance of
mis-matched files) the manifests describing an engine, and the
simulator engine itself, are held in the same source file.

This means that the engine must be included twice, with the first pass
controlled by the SIM_MANIFESTS definition.

-------------------------------------------------------------------------------
> EOF README.Cygnus