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

* objcopy.c (copy_object): Revert yesterday's change.

Browse source 
* binutils.texi, objcopy.1: Remove special mention of --set-start
	and `binary' output format.
This commit is contained in:
Ian Lance Taylor 1994-10-19 18:11:10 +00:00
parent 8b65c39307
commit a6afc09071
3 changed files with 7 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

9
binutils/binutils.texi
View file

@ -774,9 +774,8 @@ target of @samp{srec} (e.g., use @samp{-O srec}).
output target of @samp{binary} (e.g., use @samp{-O binary}). When
@code{objcopy} generates a raw binary file, it will essentially produce
a memory dump of the contents of the input object file. All symbols and
relocation information will be discarded. By default, the memory dump
will start at virtual address zero; the @samp{--set-start} option may be
used to specify a different starting point.
relocation information will be discarded. The memory dump will start at
the virtual address of the lowest section copied into the output file.
When generating an S-record or a raw binary file, it may be helpful to
use @samp{-S} to remove sections containing debugging information. In
@ -849,9 +848,7 @@ copy with the @var{-b} or @samp{--byte} option. The default is 4.
@item --set-start @var{val}
Set the address of the new file to @var{val}. Not all object file
formats support setting the start address. When using the @samp{binary}
output file format, the start address sets the virtual address of the
first byte in the binary output file.
formats support setting the start address.
@item --adjust-start @var{incr}
Adjust the start address by adding @var{incr}. Not all object file