* configure.in: Don't set PICFLAG on ix86-cygwin32.

[deliverable/binutils-gdb.git] / sim / README-HACKING

diff --git a/sim/README-HACKING b/sim/README-HACKING
index 93ccf3478f4a0c0cdb1b4e8a6daac1fcfa57acdd..fd6aae19f91f284a35208760c4cbaef1a9ded173 100644 (file)
--- a/sim/README-HACKING
+++ b/sim/README-HACKING
@@ -1,11 +1,13 @@
 This is a loose collection of notes for people hacking on simulators.
-If this document gets big enough it can be prettied it up then.
+If this document gets big enough it can be prettied up then.
 
 Contents
 
 - The "common" directory
 - Common Makefile Support
+- TAGS support
 - Generating "configure" files
+- tconfig.in
 \f
 The "common" directory
 ======================
@@ -70,9 +72,13 @@ The Makefile.in of a simulator using the common framework should look like:
 # These variables are given default values in COMMON_PRE_CONFIG_FRAG.
 # We override the ones we need to here.
 # Not all of these need to be mentioned, only the necessary ones.
+# In fact it is better to *not* mention ones if the value is the default.
 
 # List of object files, less common parts.
 SIM_OBJS =
+# List of extra dependencies.
+# Generally this consists of simulator specific files included by sim-main.h.
+SIM_EXTRA_DEPS =
 # List of flags to always pass to $(CC).
 SIM_EXTRA_CFLAGS =
 # List of extra libraries to link with.
@@ -101,6 +107,22 @@ The resulting Makefile is created by doing autoconf substitions on
 both the target's Makefile.in and Make-common.in, and inserting
 the two pieces of Make-common.in into the target's Makefile.in at
 COMMON_{PRE,POST}_CONFIG_FRAG.
+
+Note that SIM_EXTRA_{INSTALL,CLEAN} could be removed and "::" targets
+could be used instead.  However, it's not clear yet whether "::" targets
+are portable enough.
+\f
+TAGS support
+============
+
+Many files generate program symbols at compile time.
+Such symbols can't be found with grep nor do they normally appear in
+the TAGS file.  To get around this, source files can add the comment
+
+/* TAGS: foo1 foo2 */
+
+where foo1, foo2 are program symbols.  Symbols found in such comments
+are greppable and appear in the TAGS file.
 \f
 Generating "configure" files
 ============================
@@ -120,7 +142,47 @@ renaming):
 
        $  make -f Makefile.in autoconf-changelog
        $  more */new-ChangeLog
-       $  for f in */new-ChangeLog ; do echo $f ; mv $f `dirname $f`/ChangeLog ; done
+       $  make -f Makefile.in autoconf-install
 
+In a similar vein, both the configure and config.in files can be
+updated using the sequence:
 
+       $  cd devo/sim
+       $  make -f Makefile.in autoheader-common
+       $  make -f Makefile.in autoheader-changelog
+       $  more */new-ChangeLog
+       $  make -f Makefile.in autoheader-install
+\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       If sim-types.h is included, the two
+               types signed64 and unsigned64 are
+               available.
+
+       o       The type `unsigned' is valid.
+
+However, the user should not assume:
+
+       o       `<number>LL' is acceptable.  Microsoft-C
+               doesn't reconize it.
+
+       o       `long long' or `_int64' provides a 64 bit
+               integer data type.