darlinghq/darling-gdb
1
0
Fork 0
mirror of https://github.com/darlinghq/darling-gdb.git synced 2024-11-28 22:40:24 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
2434e38489
darling-gdb/sim/mips
History
Jackie Smith Cashion 8bae0a0c48 * gencode.c: Tidied instruction decoding, and added FP instruction 
support.
* interp.c: Added dineroIII, and BSD profiling support. Also
run-time FP handling.

At the moment the options are still mostly build-time controlled,
rather than run-time. Also work still needs to be done to remove (long
long) usage (However this is trivial, just time-consuming).

The out-standing instruction work to be done is in supporting round
and trunc for FP operations, and providing better exception support.
1995-12-01 16:42:44 +00:00
..
ChangeLog * gencode.c: Tidied instruction decoding, and added FP instruction 1995-12-01 16:42:44 +00:00
configure.in Initial check-in of the MIPS simulator. Work still needs to be done on 1995-11-08 15:44:38 +00:00
gencode.c * gencode.c: Tidied instruction decoding, and added FP instruction 1995-12-01 16:42:44 +00:00
interp.c * gencode.c: Tidied instruction decoding, and added FP instruction 1995-12-01 16:42:44 +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 Initial check-in of the MIPS simulator. Work still needs to be done on 1995-11-08 15:44:38 +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