* mmo.c: Adjust documentation tags to use texinfo 4 features.

diff --git a/bfd/ChangeLog b/bfd/ChangeLog
index 24bb2e6b4d0ae80603d8b0180766a8b01798705f..207bb436e85d8c1e6d9f4073f427205ac606d8dc 100644 (file)
--- a/bfd/ChangeLog
+++ b/bfd/ChangeLog
@@ -1,3 +1,7 @@
+2001-11-19  Hans-Peter Nilsson  <hp@bitrange.com>
+
+       * mmo.c: Adjust documentation tags to use texinfo 4 features.
+
 2001-11-15  Daniel Jacobowitz  <drow@mvista.com>
 
        * elflink.h (elf_reloc_symbol_deleted_p): Catch all relocs against

diff --git a/bfd/mmo.c b/bfd/mmo.c
index 8bb509518f3f3e6df3fb48ca1ebdc1ab0676eb8b..e9034de3db79c2033957b8f1707dfe3d221998a1 100644 (file)
--- a/bfd/mmo.c
+++ b/bfd/mmo.c
@@ -27,15 +27,15 @@ SECTION
 
        The mmo object format is used exclusively together with Professor
        Donald E.@: Knuth's educational 64-bit processor MMIX.  The simulator
-       @emph{mmix} which is available at
-       @emph{http://www-cs-faculty.stanford.edu/~knuth/programs/mmix.tar.gz}
+       @command{mmix} which is available at
+       @url{http://www-cs-faculty.stanford.edu/~knuth/programs/mmix.tar.gz}
        understands this format.  That package also includes a combined
-       assembler and linker called @emph{mmixal}.  The mmo format has
+       assembler and linker called @command{mmixal}.  The mmo format has
        no advantages feature-wise compared to e.g. ELF.  It is a simple
        non-relocatable object format with no support for archives or
        debugging information, except for symbol value information and
        line numbers (which is not yet implemented in BFD).  See
-       @emph{http://www-cs-faculty.stanford.edu/~knuth/mmix.html} for more
+       @url{http://www-cs-faculty.stanford.edu/~knuth/mmix.html} for more
        information about MMIX.  The ELF format is used for intermediate
        object files in the BFD implementation.
 
@@ -68,7 +68,7 @@ SUBSECTION
        two remaining bytes, called the @samp{Y} and @samp{Z} fields, or
        the @samp{YZ} field (a 16-bit big-endian number), are used for
        various purposes different for each lopcode.  As documented in
-       @emph{http://www-cs-faculty.stanford.edu/~knuth/mmixal-intro.ps.gz},
+       @url{http://www-cs-faculty.stanford.edu/~knuth/mmixal-intro.ps.gz},
        the lopcodes are:
 
        There is provision for specifying ``special data'' of 65536
@@ -1210,7 +1210,7 @@ SUBSECTION
        Symbol table format
 
        From mmixal.w (or really, the generated mmixal.tex) in
-       @emph{http://www-cs-faculty.stanford.edu/~knuth/programs/mmix.tar.gz}):
+       @url{http://www-cs-faculty.stanford.edu/~knuth/programs/mmix.tar.gz}):
        ``Symbols are stored and retrieved by means of a @samp{ternary
        search trie}, following ideas of Bentley and Sedgewick. (See
        ACM--SIAM Symp.@: on Discrete Algorithms @samp{8} (1997), 360--369;