- Common Makefile Support
- TAGS support
- Generating "configure" files
-- tconfig.in
- C Language Assumptions
- "dump" commands under gdb
\f
A common configuration framework is available for simulators that want
to use it. The common framework exists to remove a lot of duplication
-in configure.in and Makefile.in, and it also provides a foundation for
+in configure.ac and Makefile.in, and it also provides a foundation for
enhancing the simulators uniformly (e.g. the more they share in common
the easier a feature added to one is added to all).
-The configure.in of a simulator using the common framework should look like:
+The configure.ac of a simulator using the common framework should look like:
--- snip ---
dnl Process this file with autoconf to produce a configure script.
$ make ChangeLog=MyChangeLog ....
\f
-tconfig.in
-==========
-
-File tconfig.in defines one or more target configuration macros
-(e.g. a tm.h file). There are very few that need defining.
-For a list of all of them, see common/tconfig.in.
-It contains them all, commented out.
-The intent is that a new port can just copy this file and
-define the ones it needs.
-\f
C Language Assumptions
======================
The programmer may assume that the simulator is being built using an
ANSI C compiler that supports a 64 bit data type. Consequently:
- o prototypes can be used (although using
- PARAMS() and K&R declarations wouldn't
- go astray).
+ o prototypes can be used
o If sim-types.h is included, the two
types signed64 and unsigned64 are