aboutsummaryrefslogtreecommitdiff
path: root/bfd
diff options
context:
space:
mode:
authorHans-Peter Nilsson <hp@axis.com>2001-06-20 22:23:23 +0000
committerHans-Peter Nilsson <hp@axis.com>2001-06-20 22:23:23 +0000
commitd1d013c334d753a24f0c105eec070adc84c64404 (patch)
tree5abd516dbc829b8112ff1218d73347e2fc4c9d9c /bfd
parent9317eaccac71a58fca33b448bfac3da8e2efe409 (diff)
downloadgdb-d1d013c334d753a24f0c105eec070adc84c64404.zip
gdb-d1d013c334d753a24f0c105eec070adc84c64404.tar.gz
gdb-d1d013c334d753a24f0c105eec070adc84c64404.tar.bz2
* bfdint.texi (BFD relocation functions) <different formats>:
Mention that the GNU linker is aware of input-output format restrictions when generating relocatable output. Make new paragraph for final-link case. (BFD target vector swap): Fix typo.
Diffstat (limited to 'bfd')
-rw-r--r--bfd/doc/ChangeLog8
-rw-r--r--bfd/doc/bfdint.texi13
2 files changed, 16 insertions, 5 deletions
diff --git a/bfd/doc/ChangeLog b/bfd/doc/ChangeLog
index 5704b5a..68a6842 100644
--- a/bfd/doc/ChangeLog
+++ b/bfd/doc/ChangeLog
@@ -1,3 +1,11 @@
+2001-06-21 Hans-Peter Nilsson <hp@axis.com>
+
+ * bfdint.texi (BFD relocation functions) <different formats>:
+ Mention that the GNU linker is aware of input-output format
+ restrictions when generating relocatable output. Make new
+ paragraph for final-link case.
+ (BFD target vector swap): Fix typo.
+
2001-01-25 Kazu Hirata <kazu@hxi.com>
* chew.c: Do not output trailing whitespaces in type and
diff --git a/bfd/doc/bfdint.texi b/bfd/doc/bfdint.texi
index 5aa8ed3..d027aad 100644
--- a/bfd/doc/bfdint.texi
+++ b/bfd/doc/bfdint.texi
@@ -379,7 +379,7 @@ vectors which use the same sets of functions.
@node BFD target vector swap
@subsection Swapping functions
-Every target vector has fuction pointers used for swapping information
+Every target vector has function pointers used for swapping information
in and out of the target representation. There are two sets of
functions: one for data information, and one for header information.
Each set has three sizes: 64-bit, 32-bit, and 16-bit. Each size has
@@ -1291,10 +1291,13 @@ doing a link in which the output object file format is S-records.
@item
Using the linker to generate relocateable output in a different object
file format is impossible in the general case, so you generally don't
-have to worry about that. Linking input files of different object file
-formats together is quite unusual, but if you're really dedicated you
-may want to consider testing this case, both when the output object file
-format is the same as your format, and when it is different.
+have to worry about that. The GNU linker makes sure to stop that from
+happening when an input file in a different format has relocations.
+
+Linking input files of different object file formats together is quite
+unusual, but if you're really dedicated you may want to consider testing
+this case, both when the output object file format is the same as your
+format, and when it is different.
@end itemize
@node BFD relocation codes