FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Initial check-in of the MIPS simulator. Work still needs to be done on

Browse source 
the run-time support code (interp.c) to provide better tracing, and
also to add profiling and architecture specific support. At the moment
the simulator has a fixed size, fixed address memory area, and
simulates a subset of the IDT monitor calls (enough to execute test
programs).

The other major feature (could even be a bug) is that the simulator
makes use of the GCC "long long" extension. Work has been started to
make this a build configuration option... but there is still a lot of
this to be done.
This commit is contained in:
Jackie Smith Cashion 1995-11-08 15:44:38 +00:00
parent 9cacb47b67
commit 8ad5773724
4 changed files with 2165 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

38
sim/mips/README.Cygnus Normal file
View file

@ -0,0 +1,38 @@
> 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