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

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

Browse source
This commit is contained in:
Hans-Peter Nilsson 2001-11-19 01:22:45 +00:00
parent 13f7ad5861
commit 6eeb40b2c0
2 changed files with 10 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
bfd/ChangeLog
View file

@ -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> 2001-11-15 Daniel Jacobowitz <drow@mvista.com>
* elflink.h (elf_reloc_symbol_deleted_p): Catch all relocs against * elflink.h (elf_reloc_symbol_deleted_p): Catch all relocs against

12
bfd/mmo.c
View file

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