binutils-gdb

History

David Edelsohn 9d52bcb7f0 * Makefile.in (SIM_OBJS): Add sim-load.o. * interp.c: #include bfd.h. (target_byte_order): Delete. (sim_kind, myname, big_endian_p): New static locals. (sim_open): Set sim_kind, myname. Move call to set_endianness to after argument parsing. Recognize -E arg, set endianness accordingly. (sim_load): Return SIM_RC. New arg abfd. Call sim_load_file to load file into simulator. Set PC from bfd. (sim_create_inferior): Return SIM_RC. Delete arg start_address. (set_endianness): Use big_endian_p instead of target_byte_order.		1997-04-17 10:23:48 +00:00
..
.Sanitize	Add r5900	1997-02-11 13:26:34 +00:00
ChangeLog	* Makefile.in (SIM_OBJS): Add sim-load.o.	1997-04-17 10:23:48 +00:00
config.in	Get configure to define RETSIGTYPE	1997-04-07 05:58:59 +00:00
configure	Get configure to define RETSIGTYPE	1997-04-07 05:58:59 +00:00
configure.in	Add r5900	1997-02-11 13:26:34 +00:00
gencode.c	Correct the overloaded DOUBLEWORD problem	1997-02-26 23:49:19 +00:00
interp.c	* Makefile.in (SIM_OBJS): Add sim-load.o.	1997-04-17 10:23:48 +00:00
Makefile.in	* Makefile.in (@COMMON_MAKEFILE_FRAG): Use	1997-02-04 21:42:27 +00:00
README.Cygnus
support.h	Add r5900	1997-02-11 13:26:34 +00:00
tconfig.in	* Makefile.in: Delete stuff moved to ../common/Make-common.in.	1996-11-20 10:00:42 +00:00

README.Cygnus

> 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