OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

* 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.
This commit is contained in:
Hans-Peter Nilsson 2001-06-20 22:23:23 +00:00
parent 9317eaccac
commit d1d013c334
2 changed files with 16 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
bfd/doc/ChangeLog
View File

@ -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

13
bfd/doc/bfdint.texi
View File

@ -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