Toolchain/binutils-gdb
1
0
Fork 0
forked from Imagelibrary/binutils-gdb
Code Pull Requests Activity

* 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

10
binutils/objcopy.1
View File

@@ -70,10 +70,8 @@ When
.B 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
.B --set-start
option may be used to specify a different starting point.
information will be discarded. The memory dump will start at the
virtual address of the lowest section copied into the output file.
.PP
When generating an S-record or a raw binary file, it may be helpful to
use
@@ -140,9 +138,7 @@ The interleave is ignored if neither \fB\-b\fP nor \fB\-\-byte\fP is given.
.TP
.B \fB\-\-set\-start=\fIval
Set the start address of the new file to \fIval\fP. Not all object
file formats support setting the start address. When using the
\fBbinary\fP output file format, the start address sets the virtual
address of the first byte in the binary output file.
file formats support setting the start address.
.TP
.B \fB\-\-adjust\-start=\fIincr
Adjust the start address by adding \fIincr\fP. Not all object file