a77aa7ec4b
* Make-common.in (CSEARCH): Do not include the gdb directory in the search path. * Make-common.in (SIM_ENDIAN, SIM_HOSTENDIAN, SIM_INLINE, SIM_WARNING): Drop, requiring the simulator specific Makefile.in to explicitly incorporate these. * aclocal.m4 (--enable-sim-alignment); New option. Strongly specify the alignment restrictions of the target architecture - without this option all alignment restrictions are accomodated. (--enable-sim-assert): New option. Conditionally compile in assertion statements. (--enable-sim-float): New option. Strongly specify the target's floating point support. (--enable-sim-hardware): New option. Specify the hardware devices included in the simulation. (--enable-sim-packages): New option. Specify the hardware packages included in the simulation. (--enable-sim-regparm): New option. Specify that parameters be passed in registers instead of on the stack. (--enable-sim-reserved-bits): New option. Specify that reserved bits within an instruction are are correctly set. (--enable-sim-smp): New option. Specify the level of SMP support to be included in the simulator. (--enable-sim-stdcall): New option. Specify an alternative function call convention. (--enable-sim-xor-endian): New option. Configure xor-endian support used by some targets to implement bi-endian support. |
||
---|---|---|
.. | ||
.Sanitize | ||
ChangeLog | ||
configure | ||
configure.in | ||
gencode.c | ||
interp.c | ||
Makefile.in | ||
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