binutils-gdb/sim/mips
Gavin Romig-Koch 7afa8d4edc * gencode.c: Add r3900 (tx39).
* gencode.c: Fix some configuration problems by improving
	the relationship between tx19 and tx39.
1997-09-19 13:39:55 +00:00
..
.Sanitize Support tx19 sanitation. 1997-09-10 04:53:18 +00:00
ChangeLog * gencode.c: Add r3900 (tx39). 1997-09-19 13:39:55 +00:00
config.in Get configure to define RETSIGTYPE 1997-04-07 05:58:59 +00:00
configure Update to reflect change to sim/common/aclocal.m4 (allow sim/common 1997-09-15 08:25:04 +00:00
configure.in tx19 and related necessary changes. 1997-09-07 20:33:22 +00:00
gencode.c * gencode.c: Add r3900 (tx39). 1997-09-19 13:39:55 +00:00
interp.c * sim/mips/interp.c: Correct some HASFPU problems. 1997-09-16 15:36:18 +00:00
Makefile.in Add ABFD argument to sim_create_inferior. Document. 1997-08-27 04:44:41 +00:00
README.Cygnus
support.h
tconfig.in

> 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