werunplugged/unplugged-vendor
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
ebc759d833
unplugged-vendor/prebuilts/xcc/linux-x86/xtensa/RI-2018.0-linux/XtensaTools/info/binutils.info

3716 lines
149 KiB
Plaintext
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This is binutils.info, produced by makeinfo version 4.8 from
/home/xpgcust/tree/RI-2019.1/ib/p4root/Xtensa/Software/binutils/binutils/doc/binutils.texi.
10/2018
Copyright (C) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011,
2012, 2013 Free Software Foundation, Inc.
Copyright (C) 1999-2013 Tensilica, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled "GNU
Free Documentation License".
This publication is provided "AS IS." Tensilica, Inc. (hereafter
"Tensilica") does not make any warranty of any kind, either expressed
or implied, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose. Information in
this document is provided solely to enable system and software
developers to use Tensilica(R) processors. Unless specifically set
forth herein, there are no express or implied patent, copyright or any
other intellectual property rights or licenses granted hereunder to
design or fabricate Tensilica integrated circuits or integrated
circuits based on the information in this document. Tensilica does not
warrant that the contents of this publication, whether individually or
as one or more groups, meets your requirements or that the publication
is error-free. This publication could include technical inaccuracies
or typographical errors. Changes may be made to the information
herein, and these changes may be incorporated in new editions of this
publication.
The following terms are trademarks or registered trademarks of
Tensilica, Inc.: FLIX, OSKit, Sea of Processors, Tensilica, Vectra,
Xplorer, XPRES, and Xtensa. All other trademarks and registered
trademarks are the property of their respective companies.

File: binutils.info, Node: Top, Next: Revisions, Up: (dir)
GNU Binary Utilities User's Guide
*********************************
This brief manual contains documentation for the GNU binary utilities
Version 2.23.2 for Xtensa Tools Version 14.
This document is distributed under the terms of the GNU Free
Documentation License. A copy of the license is included in the
section entitled "GNU Free Documentation License".
* Menu:
* Revisions:: Changes from previous versions.
* ar:: Create, modify, and extract from archives
* nm:: List symbols from object files
* objcopy:: Copy and translate object files
* objdump:: Display information from object files
* ranlib:: Generate index to archive contents
* readelf:: Display the contents of ELF format files.
* size:: List section sizes and total size
* strings:: List printable strings from files
* strip:: Discard symbols
* elfedit:: Update the ELF header of ELF files
* c++filt:: Filter to demangle encoded C++ symbols
* cxxfilt: c++filt. MS-DOS name for c++filt
* addr2line:: Convert addresses to file and line
* Common Options:: Command-line options for all utilities
* GNU Free Documentation License:: GNU Free Documentation License
* History:: History of this document.
* Binutils Index:: Index

File: binutils.info, Node: Revisions, Next: ar, Prev: Top, Up: Top
Changes from Previous Versions
******************************
The following changes were made to this document for the Xtensa Tools
version 11.0 released in the Tensilica RF-2014.0 release:
Xtensa Tools:
* Upgraded from version 2.20 to version 2.23.2 of the GNU Binary
Utilities.

File: binutils.info, Node: ar, Next: nm, Prev: Revisions, Up: Top
1 ar
****
xt-ar [-]P[MOD [RELPOS] [COUNT]] [`--target' BFDNAME] ARCHIVE [MEMBER...]
The GNU `ar' program creates, modifies, and extracts from archives.
An "archive" is a single file holding a collection of other files in a
structure that makes it possible to retrieve the original individual
files (called "members" of the archive).
The original files' contents, mode (permissions), timestamp, owner,
and group are preserved in the archive, and can be restored on
extraction.
GNU `ar' can maintain archives whose members have names of any
length; however, depending on how `ar' is configured on your system, a
limit on member-name length may be imposed for compatibility with
archive formats maintained with other tools. If it exists, the limit
is often 15 characters (typical of formats related to a.out) or 16
characters (typical of formats related to coff).
`ar' is considered a binary utility because archives of this sort
are most often used as "libraries" holding commonly needed subroutines.
`ar' creates an index to the symbols defined in relocatable object
modules in the archive when you specify the modifier `s'. Once
created, this index is updated in the archive whenever `ar' makes a
change to its contents (save for the `q' update operation). An archive
with such an index speeds up linking to the library, and allows
routines in the library to call each other without regard to their
placement in the archive.
You may use `xt-nm -s' or `xt-nm --print-armap' to list this index
table. If an archive lacks the table, another form of `ar' called
`ranlib' can be used to add just the table.
GNU `ar' can optionally create a _thin_ archive, which contains a
symbol index and references to the original copies of the member files
of the archives. Such an archive is useful for building libraries for
use within a local build, where the relocatable objects are expected to
remain available, and copying the contents of each object would only
waste time and space. Thin archives are also _flattened_, so that
adding one or more archives to a thin archive will add the elements of
the nested archive individually. The paths to the elements of the
archive are stored relative to the archive itself.
`xt-ar' insists on at least two arguments to execute: one keyletter
specifying the _operation_ (optionally accompanied by other keyletters
specifying _modifiers_), and the archive name to act on.
Most operations can also accept further MEMBER arguments, specifying
particular files to operate on.
GNU `ar' allows you to mix the operation code P and modifier flags
MOD in any order, within the first command-line argument.
If you wish, you may begin the first command-line argument with a
dash.
The P keyletter specifies what operation to execute; it may be any
of the following, but you must specify only one of them:
`d'
_Delete_ modules from the archive. Specify the names of modules to
be deleted as MEMBER...; the archive is untouched if you specify
no files to delete.
If you specify the `v' modifier, `ar' lists each module as it is
deleted.
`m'
Use this operation to _move_ members in an archive.
The ordering of members in an archive can make a difference in how
programs are linked using the library, if a symbol is defined in
more than one member.
If no modifiers are used with `m', any members you name in the
MEMBER arguments are moved to the _end_ of the archive; you can
use the `a', `b', or `i' modifiers to move them to a specified
place instead.
`p'
_Print_ the specified members of the archive, to the standard
output file. If the `v' modifier is specified, show the member
name before copying its contents to standard output.
If you specify no MEMBER arguments, all the files in the archive
are printed.
`q'
_Quick append_; Historically, add the files MEMBER... to the end of
ARCHIVE, without checking for replacement.
The modifiers `a', `b', and `i' do _not_ affect this operation;
new members are always placed at the end of the archive.
The modifier `v' makes `ar' list each file as it is appended.
Since the point of this operation is speed, the archive's symbol
table index is not updated, even if it already existed; you can
use `xt-ar s' or `xt-ranlib' explicitly to update the symbol table
index.
However, too many different systems assume quick append rebuilds
the index, so GNU `ar' implements `q' as a synonym for `r'.
`r'
Insert the files MEMBER... into ARCHIVE (with _replacement_). This
operation differs from `q' in that any previously existing members
are deleted if their names match those being added.
If one of the files named in MEMBER... does not exist, `ar'
displays an error message, and leaves undisturbed any existing
members of the archive matching that name.
By default, new members are added at the end of the file; but you
may use one of the modifiers `a', `b', or `i' to request placement
relative to some existing member.
The modifier `v' used with this operation elicits a line of output
for each file inserted, along with one of the letters `a' or `r'
to indicate whether the file was appended (no old member deleted)
or replaced.
`s'
Add an index to the archive, or update it if it already exists.
Note this command is an exception to the rule that there can only
be one command letter, as it is possible to use it as either a
command or a modifier. In either case it does the same thing.
`t'
Display a _table_ listing the contents of ARCHIVE, or those of the
files listed in MEMBER... that are present in the archive.
Normally only the member name is shown; if you also want to see
the modes (permissions), timestamp, owner, group, and size, you can
request that by also specifying the `v' modifier.
If you do not specify a MEMBER, all files in the archive are
listed.
If there is more than one file with the same name (say, `fie') in
an archive (say `b.a'), `xt-ar t b.a fie' lists only the first
instance; to see them all, you must ask for a complete listing--in
our example, `xt-ar t b.a'.
`x'
_Extract_ members (named MEMBER) from the archive. You can use
the `v' modifier with this operation, to request that `ar' list
each name as it extracts it.
If you do not specify a MEMBER, all files in the archive are
extracted.
Files cannot be extracted from a thin archive.
`--help'
Displays the list of command line options supported by `ar' and
then exits.
`--version'
Displays the version information of `ar' and then exits.
A number of modifiers (MOD) may immediately follow the P keyletter,
to specify variations on an operation's behavior:
`a'
Add new files _after_ an existing member of the archive. If you
use the modifier `a', the name of an existing archive member must
be present as the RELPOS argument, before the ARCHIVE
specification.
`b'
Add new files _before_ an existing member of the archive. If you
use the modifier `b', the name of an existing archive member must
be present as the RELPOS argument, before the ARCHIVE
specification. (same as `i').
`c'
_Create_ the archive. The specified ARCHIVE is always created if
it did not exist, when you request an update. But a warning is
issued unless you specify in advance that you expect to create it,
by using this modifier.
`D'
Operate in _deterministic_ mode. When adding files and the archive
index use zero for UIDs, GIDs, timestamps, and use consistent file
modes for all files. When this option is used, if `ar' is used
with identical options and identical input files, multiple runs
will create identical output files regardless of the input files'
owners, groups, file modes, or modification times.
If `binutils' was configured with
`--enable-deterministic-archives', then this mode is on by default.
It can be disabled with the `U' modifier, below.
`f'
Truncate names in the archive. GNU `ar' will normally permit file
names of any length. This will cause it to create archives which
are not compatible with the native `ar' program on some systems.
If this is a concern, the `f' modifier may be used to truncate file
names when putting them in the archive.
`i'
Insert new files _before_ an existing member of the archive. If
you use the modifier `i', the name of an existing archive member
must be present as the RELPOS argument, before the ARCHIVE
specification. (same as `b').
`l'
This modifier is accepted but not used.
`N'
Uses the COUNT parameter. This is used if there are multiple
entries in the archive with the same name. Extract or delete
instance COUNT of the given name from the archive.
`o'
Preserve the _original_ dates of members when extracting them. If
you do not specify this modifier, files extracted from the archive
are stamped with the time of extraction.
`P'
Use the full path name when matching names in the archive. GNU
`ar' can not create an archive with a full path name (such archives
are not POSIX complaint), but other archive creators can. This
option will cause GNU `ar' to match file names using a complete
path name, which can be convenient when extracting a single file
from an archive created by another tool.
`s'
Write an object-file index into the archive, or update an existing
one, even if no other change is made to the archive. You may use
this modifier flag either with any operation, or alone. Running
`xt-ar s' on an archive is equivalent to running `xt-ranlib' on it.
`S'
Do not generate an archive symbol table. This can speed up
building a large library in several steps. The resulting archive
can not be used with the linker. In order to build a symbol
table, you must omit the `S' modifier on the last execution of
`xt-ar', or you must run `ranlib' on the archive.
`T'
Make the specified ARCHIVE a _thin_ archive. If it already exists
and is a regular archive, the existing members must be present in
the same directory as ARCHIVE.
`u'
Normally, `xt-ar r'... inserts all files listed into the archive.
If you would like to insert _only_ those of the files you list
that are newer than existing members of the same names, use this
modifier. The `u' modifier is allowed only for the operation `r'
(replace). In particular, the combination `qu' is not allowed,
since checking the timestamps would lose any speed advantage from
the operation `q'.
`U'
Do _not_ operate in _deterministic_ mode. This is the inverse of
the `D' modifier, above: added files and the archive index will
get their actual UID, GID, timestamp, and file mode values.
This is the default unless `binutils' was configured with
`--enable-deterministic-archives'.
`v'
This modifier requests the _verbose_ version of an operation. Many
operations display additional information, such as filenames
processed, when the modifier `v' is appended.
`V'
This modifier shows the version number of `ar'.
`ar' ignores an initial option spelt `-X32_64', for compatibility
with AIX. The behaviour produced by this option is the default for GNU
`ar'. `ar' does not support any of the other `-X' options; in
particular, it does not support `-X32' which is the default for AIX
`ar'.
The optional command line switch `--target' BFDNAME specifies that
the archive members are in an object code format different from your
system's default format. See *Note Target Selection::, for more
information.

File: binutils.info, Node: nm, Next: objcopy, Prev: ar, Up: Top
2 nm
****
xt-nm [`-a'|`--debug-syms']
[`-g'|`--extern-only']
[`-B'] [`-C'|`--demangle'[=STYLE]] [`-D'|`--dynamic']
[`-S'|`--print-size'] [`-s'|`--print-armap']
[`-A'|`-o'|`--print-file-name'][`--special-syms']
[`-n'|`-v'|`--numeric-sort'] [`-p'|`--no-sort']
[`-r'|`--reverse-sort'] [`--size-sort'] [`-u'|`--undefined-only']
[`-t' RADIX|`--radix='RADIX] [`-P'|`--portability']
[`--target='BFDNAME] [`-f'FORMAT|`--format='FORMAT]
[`--defined-only'] [`-l'|`--line-numbers'] [`--no-demangle']
[`-V'|`--version'] [`-X 32_64'] [`--help'] [OBJFILE...]
[`--xtensa-core='NAME]
[`--xtensa-system='REGISTRY]
[`--xtensa-params='PATH]
[`--help'] [OBJFILE...]
GNU `nm' lists the symbols from object files OBJFILE.... If no
object files are listed as arguments, `nm' assumes the file `a.out'.
For each symbol, `nm' shows:
* The symbol value, in the radix selected by options (see below), or
hexadecimal by default.
* The symbol type. At least the following types are used; others
are, as well, depending on the object file format. If lowercase,
the symbol is usually local; if uppercase, the symbol is global
(external). There are however a few lowercase symbols that are
shown for special global symbols (`u', `v' and `w').
`A'
The symbol's value is absolute, and will not be changed by
further linking.
`B'
`b'
The symbol is in the uninitialized data section (known as
BSS).
`C'
The symbol is common. Common symbols are uninitialized data.
When linking, multiple common symbols may appear with the
same name. If the symbol is defined anywhere, the common
symbols are treated as undefined references. For more
details on common symbols, see the discussion of -warn-common
in *Note Command Line Options: (ld)Options.
`D'
`d'
The symbol is in the initialized data section.
`G'
`g'
The symbol is in an initialized data section for small
objects. Some object file formats permit more efficient
access to small data objects, such as a global int variable
as opposed to a large global array.
`i'
For ELF format files this indicates that the symbol is an
indirect function. This is a GNU extension to the standard
set of ELF symbol types. It indicates a symbol which if
referenced by a relocation does not evaluate to its address,
but instead must be invoked at runtime. The runtime
execution will then return the value to be used in the
relocation.
`N'
The symbol is a debugging symbol.
`p'
The symbols is in a stack unwind section.
`R'
`r'
The symbol is in a read only data section.
`S'
`s'
The symbol is in an uninitialized data section for small
objects.
`T'
`t'
The symbol is in the text (code) section.
`U'
The symbol is undefined.
`u'
The symbol is a unique global symbol. This is a GNU
extension to the standard set of ELF symbol bindings. For
such a symbol the dynamic linker will make sure that in the
entire process there is just one symbol with this name and
type in use.
`V'
`v'
The symbol is a weak object. When a weak defined symbol is
linked with a normal defined symbol, the normal defined
symbol is used with no error. When a weak undefined symbol
is linked and the symbol is not defined, the value of the
weak symbol becomes zero with no error.
`W'
`w'
The symbol is a weak symbol that has not been specifically
tagged as a weak object symbol. When a weak defined symbol
is linked with a normal defined symbol, the normal defined
symbol is used with no error. When a weak undefined symbol
is linked and the symbol is not defined, the value of the
symbol is determined in a system-specific manner without
error. On some systems, uppercase indicates that a default
value has been specified.
`-'
The symbol is a stabs symbol in an a.out object file. In
this case, the next values printed are the stabs other field,
the stabs desc field, and the stab type. Stabs symbols are
used to hold debugging information.
`?'
The symbol type is unknown, or object file format specific.
* The symbol name.
The long and short forms of options, shown here as alternatives, are
equivalent.
`-A'
`-o'
`--print-file-name'
Precede each symbol by the name of the input file (or archive
member) in which it was found, rather than identifying the input
file once only, before all of its symbols.
`-a'
`--debug-syms'
Display all symbols, even debugger-only symbols; normally these
are not listed.
`-B'
The same as `--format=bsd' (for compatibility with the MIPS `nm').
`-C'
`--demangle[=STYLE]'
Decode ("demangle") low-level symbol names into user-level names.
Besides removing any initial underscore prepended by the system,
this makes C++ function names readable. Different compilers have
different mangling styles. The optional demangling style argument
can be used to choose an appropriate demangling style for your
compiler. *Note c++filt::, for more information on demangling.
`--no-demangle'
Do not demangle low-level symbol names. This is the default.
`-D'
`--dynamic'
Display the dynamic symbols rather than the normal symbols. This
is only meaningful for dynamic objects, such as certain types of
shared libraries.
`-f FORMAT'
`--format=FORMAT'
Use the output format FORMAT, which can be `bsd', `sysv', or
`posix'. The default is `bsd'. Only the first character of
FORMAT is significant; it can be either upper or lower case.
`-g'
`--extern-only'
Display only external symbols.
`-l'
`--line-numbers'
For each symbol, use debugging information to try to find a
filename and line number. For a defined symbol, look for the line
number of the address of the symbol. For an undefined symbol,
look for the line number of a relocation entry which refers to the
symbol. If line number information can be found, print it after
the other symbol information.
`-n'
`-v'
`--numeric-sort'
Sort symbols numerically by their addresses, rather than
alphabetically by their names.
`-p'
`--no-sort'
Do not bother to sort the symbols in any order; print them in the
order encountered.
`-P'
`--portability'
Use the POSIX.2 standard output format instead of the default
format. Equivalent to `-f posix'.
`-S'
`--print-size'
Print both value and size of defined symbols for the `bsd' output
style.
`-s'
`--print-armap'
When listing symbols from archive members, include the index: a
mapping (stored in the archive by `ar' or `ranlib') of which
modules contain definitions for which names.
`-r'
`--reverse-sort'
Reverse the order of the sort (whether numeric or alphabetic); let
the last come first.
`--size-sort'
Sort symbols by size. The size is computed as the difference
between the value of the symbol and the value of the symbol with
the next higher value. If the `bsd' output format is used the
size of the symbol is printed, rather than the value, and `-S'
must be used in order both size and value to be printed.
`--special-syms'
Display symbols which have a target-specific special meaning.
These symbols are usually used by the target for some special
processing and are not normally helpful when included included in
the normal symbol lists. For example for ARM targets this option
would skip the mapping symbols used to mark transitions between
ARM code, THUMB code and data.
`-t RADIX'
`--radix=RADIX'
Use RADIX as the radix for printing the symbol values. It must be
`d' for decimal, `o' for octal, or `x' for hexadecimal.
`--target=BFDNAME'
Specify an object code format other than your system's default
format. *Note Target Selection::, for more information.
`-u'
`--undefined-only'
Display only undefined symbols (those external to each object
file).
`--defined-only'
Display only defined symbols for each object file.
`-V'
`--version'
Show the version number of `nm' and exit.
`-X'
This option is ignored for compatibility with the AIX version of
`nm'. It takes one parameter which must be the string `32_64'.
The default mode of AIX `nm' corresponds to `-X 32', which is not
supported by GNU `nm'.
`--xtensa-core=NAME'
Specify the name of an Xtensa processor core configuration to use.
The configuration information is taken from the entry for NAME in
the Xtensa core registry (see the `--xtensa-system' option). If
this option is not specified, the Xtensa core name is either the
value of the `XTENSA_CORE' environment variable or "default" if
that variable is not set.
`--xtensa-system=REGISTRY'
Specify a directory to be used as the Xtensa core registry. If
this option is not set, the `XTENSA_SYSTEM' environment variable
specifies the Xtensa registry, and if that is not set, the default
registry, `<xtensa_tools_root>/config', is used. Please see the
`Xtensa Software Development Toolkit User's Guide' for more
information about Xtensa core registries.
`--xtensa-params=PATH'
Specify the location of the parameter file in a TIE Development Kit
(TDK) that was produced by running the TIE Compiler (tc). If PATH
identifies a directory rather than a file, the parameters are read
from a file named `default-params' if it exists in that directory.
The parameter file may also be specified by setting the
`XTENSA_PARAMS' environment variable. The `--xtensa-params'
option takes precedence over the environment variable. See the
`Tensilica Instruction Extension (TIE) Language User's Guide' for
more information.
`--help'
Show a summary of the options to `nm' and exit.

File: binutils.info, Node: objcopy, Next: objdump, Prev: nm, Up: Top
3 objcopy
*********
xt-objcopy [`-F' BFDNAME|`--target='BFDNAME]
[`-I' BFDNAME|`--input-target='BFDNAME]
[`-O' BFDNAME|`--output-target='BFDNAME]
[`-B' BFDARCH|`--binary-architecture='BFDARCH]
[`-S'|`--strip-all']
[`-g'|`--strip-debug']
[`-K' SYMBOLNAME|`--keep-symbol='SYMBOLNAME]
[`-N' SYMBOLNAME|`--strip-symbol='SYMBOLNAME]
[`--strip-unneeded-symbol='SYMBOLNAME]
[`-G' SYMBOLNAME|`--keep-global-symbol='SYMBOLNAME]
[`--localize-hidden']
[`-L' SYMBOLNAME|`--localize-symbol='SYMBOLNAME]
[`--globalize-symbol='SYMBOLNAME]
[`-W' SYMBOLNAME|`--weaken-symbol='SYMBOLNAME]
[`-w'|`--wildcard']
[`-x'|`--discard-all']
[`-X'|`--discard-locals']
[`-b' BYTE|`--byte='BYTE]
[`-i' [BREADTH]|`--interleave'[=BREADTH]]
[`--interleave-width='WIDTH]
[`-j' SECTIONNAME|`--only-section='SECTIONNAME]
[`-R' SECTIONNAME|`--remove-section='SECTIONNAME]
[`-p'|`--preserve-dates']
[`-D'|`--enable-deterministic-archives']
[`-U'|`--disable-deterministic-archives']
[`--debugging']
[`--gap-fill='VAL]
[`--pad-to='ADDRESS]
[`--set-start='VAL]
[`--adjust-start='INCR]
[`--change-addresses='INCR]
[`--change-section-address' SECTION{=,+,-}VAL]
[`--change-section-lma' SECTION{=,+,-}VAL]
[`--change-section-vma' SECTION{=,+,-}VAL]
[`--change-warnings'] [`--no-change-warnings']
[`--set-section-flags' SECTION=FLAGS]
[`--add-section' SECTIONNAME=FILENAME]
[`--rename-section' OLDNAME=NEWNAME[,FLAGS]]
[`--change-leading-char'] [`--remove-leading-char']
[`--reverse-bytes='NUM]
[`--srec-len='IVAL] [`--srec-forceS3']
[`--redefine-sym' OLD=NEW]
[`--redefine-syms='FILENAME]
[`--weaken']
[`--keep-symbols='FILENAME]
[`--strip-symbols='FILENAME]
[`--strip-unneeded-symbols='FILENAME]
[`--keep-global-symbols='FILENAME]
[`--localize-symbols='FILENAME]
[`--globalize-symbols='FILENAME]
[`--weaken-symbols='FILENAME]
[`--alt-machine-code='INDEX]
[`--prefix-symbols='STRING]
[`--prefix-sections='STRING]
[`--prefix-alloc-sections='STRING]
[`--add-gnu-debuglink='PATH-TO-FILE]
[`--keep-file-symbols']
[`--only-keep-debug']
[`--strip-dwo']
[`--extract-dwo']
[`--extract-symbol']
[`--writable-text']
[`--readonly-text']
[`--pure']
[`--impure']
[`--xtensa-core='NAME]
[`--xtensa-system='REGISTRY]
[`--xtensa-params='PATH]
[`-v'|`--verbose']
[`-V'|`--version']
[`--help'] [`--info']
INFILE [OUTFILE]
The GNU `objcopy' utility copies the contents of an object file to
another. `objcopy' uses the GNU BFD Library to read and write the
object files. It can write the destination object file in a format
different from that of the source object file. The exact behavior of
`objcopy' is controlled by command-line options. Note that `objcopy'
should be able to copy a fully linked file between any two formats.
However, copying a relocatable object file between any two formats may
not work as expected.
`objcopy' creates temporary files to do its translations and deletes
them afterward. `objcopy' uses BFD to do all its translation work; it
has access to all the formats described in BFD and thus is able to
recognize most formats without being told explicitly.
`objcopy' can be used to generate S-records by using an output
target of `srec' (e.g., use `-O srec').
`objcopy' can be used to generate a raw binary file by using an
output target of `binary' (e.g., use `-O binary'). When `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. The memory dump will start at the load
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 `-S' to remove sections containing debugging information. In
some cases `-R' will be useful to remove sections which contain
information that is not needed by the binary file.
Note--`objcopy' is not able to change the endianness of its input
files. If the input format has an endianness (some formats do not),
`objcopy' can only copy the inputs into file formats that have the same
endianness or which have no endianness (e.g., `srec'). (However, see
the `--reverse-bytes' option.)
`INFILE'
`OUTFILE'
The input and output files, respectively. If you do not specify
OUTFILE, `objcopy' creates a temporary file and destructively
renames the result with the name of INFILE.
`-I BFDNAME'
`--input-target=BFDNAME'
Consider the source file's object format to be BFDNAME, rather than
attempting to deduce it. *Note Target Selection::, for more
information.
`-O BFDNAME'
`--output-target=BFDNAME'
Write the output file using the object format BFDNAME. *Note
Target Selection::, for more information.
`-F BFDNAME'
`--target=BFDNAME'
Use BFDNAME as the object format for both the input and the output
file; i.e., simply transfer data from source to destination with no
translation. *Note Target Selection::, for more information.
`-B BFDARCH'
`--binary-architecture=BFDARCH'
Useful when transforming a architecture-less input file into an
object file. In this case the output architecture can be set to
BFDARCH. This option will be ignored if the input file has a
known BFDARCH. You can access this binary data inside a program
by referencing the special symbols that are created by the
conversion process. These symbols are called
_binary_OBJFILE_start, _binary_OBJFILE_end and
_binary_OBJFILE_size. e.g. you can transform a picture file into
an object file and then access it in your code using these symbols.
`-j SECTIONNAME'
`--only-section=SECTIONNAME'
Copy only the named section from the input file to the output file.
This option may be given more than once. Note that using this
option inappropriately may make the output file unusable.
`-R SECTIONNAME'
`--remove-section=SECTIONNAME'
Remove any section named SECTIONNAME from the output file. This
option may be given more than once. Note that using this option
inappropriately may make the output file unusable.
`-S'
`--strip-all'
Do not copy relocation and symbol information from the source file.
`-g'
`--strip-debug'
Do not copy debugging symbols or sections from the source file.
`--strip-unneeded'
Strip all symbols that are not needed for relocation processing.
`-K SYMBOLNAME'
`--keep-symbol=SYMBOLNAME'
When stripping symbols, keep symbol SYMBOLNAME even if it would
normally be stripped. This option may be given more than once.
`-N SYMBOLNAME'
`--strip-symbol=SYMBOLNAME'
Do not copy symbol SYMBOLNAME from the source file. This option
may be given more than once.
`--strip-unneeded-symbol=SYMBOLNAME'
Do not copy symbol SYMBOLNAME from the source file unless it is
needed by a relocation. This option may be given more than once.
`-G SYMBOLNAME'
`--keep-global-symbol=SYMBOLNAME'
Keep only symbol SYMBOLNAME global. Make all other symbols local
to the file, so that they are not visible externally. This option
may be given more than once.
`--localize-hidden'
In an ELF object, mark all symbols that have hidden or internal
visibility as local. This option applies on top of
symbol-specific localization options such as `-L'.
`-L SYMBOLNAME'
`--localize-symbol=SYMBOLNAME'
Make symbol SYMBOLNAME local to the file, so that it is not
visible externally. This option may be given more than once.
`-W SYMBOLNAME'
`--weaken-symbol=SYMBOLNAME'
Make symbol SYMBOLNAME weak. This option may be given more than
once.
`--globalize-symbol=SYMBOLNAME'
Give symbol SYMBOLNAME global scoping so that it is visible
outside of the file in which it is defined. This option may be
given more than once.
`-w'
`--wildcard'
Permit regular expressions in SYMBOLNAMEs used in other command
line options. The question mark (?), asterisk (*), backslash (\)
and square brackets ([]) operators can be used anywhere in the
symbol name. If the first character of the symbol name is the
exclamation point (!) then the sense of the switch is reversed for
that symbol. For example:
-w -W !foo -W fo*
would cause objcopy to weaken all symbols that start with "fo"
except for the symbol "foo".
`-x'
`--discard-all'
Do not copy non-global symbols from the source file.
`-X'
`--discard-locals'
Do not copy compiler-generated local symbols. (These usually
start with `L' or `.'.)
`-b BYTE'
`--byte=BYTE'
If interleaving has been enabled via the `--interleave' option
then start the range of bytes to keep at the BYTEth byte. BYTE
can be in the range from 0 to BREADTH-1, where BREADTH is the
value given by the `--interleave' option.
`-i [BREADTH]'
`--interleave[=BREADTH]'
Only copy a range out of every BREADTH bytes. (Header data is not
affected). Select which byte in the range begins the copy with
the `--byte' option. Select the width of the range with the
`--interleave-width' option.
This option is useful for creating files to program ROM. It is
typically used with an `srec' output target. Note that `objcopy'
will complain if you do not specify the `--byte' option as well.
The default interleave breadth is 4, so with `--byte' set to 0,
`objcopy' would copy the first byte out of every four bytes from
the input to the output.
`--interleave-width=WIDTH'
When used with the `--interleave' option, copy WIDTH bytes at a
time. The start of the range of bytes to be copied is set by the
`--byte' option, and the extent of the range is set with the
`--interleave' option.
The default value for this option is 1. The value of WIDTH plus
the BYTE value set by the `--byte' option must not exceed the
interleave breadth set by the `--interleave' option.
This option can be used to create images for two 16-bit flashes
interleaved in a 32-bit bus by passing `-b 0 -i 4
--interleave-width=2' and `-b 2 -i 4 --interleave-width=2' to two
`objcopy' commands. If the input was '12345678' then the outputs
would be '1256' and '3478' respectively.
`-p'
`--preserve-dates'
Set the access and modification dates of the output file to be the
same as those of the input file.
`-D'
`--enable-deterministic-archives'
Operate in _deterministic_ mode. When copying archive members and
writing the archive index, use zero for UIDs, GIDs, timestamps,
and use consistent file modes for all files.
If `binutils' was configured with
`--enable-deterministic-archives', then this mode is on by default.
It can be disabled with the `-U' option, below.
`-U'
`--disable-deterministic-archives'
Do _not_ operate in _deterministic_ mode. This is the inverse of
the `-D' option, above: when copying archive members and writing
the archive index, use their actual UID, GID, timestamp, and file
mode values.
This is the default unless `binutils' was configured with
`--enable-deterministic-archives'.
`--debugging'
Convert debugging information, if possible. This is not the
default because only certain debugging formats are supported, and
the conversion process can be time consuming.
`--gap-fill VAL'
Fill gaps between sections with VAL. This operation applies to
the _load address_ (LMA) of the sections. It is done by increasing
the size of the section with the lower address, and filling in the
extra space created with VAL.
`--pad-to ADDRESS'
Pad the output file up to the load address ADDRESS. This is done
by increasing the size of the last section. The extra space is
filled in with the value specified by `--gap-fill' (default zero).
`--set-start VAL'
Set the start address of the new file to VAL. Not all object file
formats support setting the start address.
`--change-start INCR'
`--adjust-start INCR'
Change the start address by adding INCR. Not all object file
formats support setting the start address.
`--change-addresses INCR'
`--adjust-vma INCR'
Change the VMA and LMA addresses of all sections, as well as the
start address, by adding INCR. Some object file formats do not
permit section addresses to be changed arbitrarily. Note that
this does not relocate the sections; if the program expects
sections to be loaded at a certain address, and this option is
used to change the sections such that they are loaded at a
different address, the program may fail.
`--change-section-address SECTION{=,+,-}VAL'
`--adjust-section-vma SECTION{=,+,-}VAL'
Set or change both the VMA address and the LMA address of the named
SECTION. If `=' is used, the section address is set to VAL.
Otherwise, VAL is added to or subtracted from the section address.
See the comments under `--change-addresses', above. If SECTION
does not exist in the input file, a warning will be issued, unless
`--no-change-warnings' is used.
`--change-section-lma SECTION{=,+,-}VAL'
Set or change the LMA address of the named SECTION. The LMA
address is the address where the section will be loaded into
memory at program load time. Normally this is the same as the VMA
address, which is the address of the section at program run time,
but on some systems, especially those where a program is held in
ROM, the two can be different. If `=' is used, the section
address is set to VAL. Otherwise, VAL is added to or subtracted
from the section address. See the comments under
`--change-addresses', above. If SECTION does not exist in the
input file, a warning will be issued, unless
`--no-change-warnings' is used.
`--change-section-vma SECTION{=,+,-}VAL'
Set or change the VMA address of the named SECTION. The VMA
address is the address where the section will be located once the
program has started executing. Normally this is the same as the
LMA address, which is the address where the section will be loaded
into memory, but on some systems, especially those where a program
is held in ROM, the two can be different. If `=' is used, the
section address is set to VAL. Otherwise, VAL is added to or
subtracted from the section address. See the comments under
`--change-addresses', above. If SECTION does not exist in the
input file, a warning will be issued, unless
`--no-change-warnings' is used.
`--change-warnings'
`--adjust-warnings'
If `--change-section-address' or `--change-section-lma' or
`--change-section-vma' is used, and the named section does not
exist, issue a warning. This is the default.
`--no-change-warnings'
`--no-adjust-warnings'
Do not issue a warning if `--change-section-address' or
`--adjust-section-lma' or `--adjust-section-vma' is used, even if
the named section does not exist.
`--set-section-flags SECTION=FLAGS'
Set the flags for the named section. The FLAGS argument is a
comma separated string of flag names. The recognized names are
`alloc', `contents', `load', `noload', `readonly', `code', `data',
`rom', `share', and `debug'. You can set the `contents' flag for
a section which does not have contents, but it is not meaningful
to clear the `contents' flag of a section which does have
contents-just remove the section instead. Not all flags are
meaningful for all object file formats.
`--add-section SECTIONNAME=FILENAME'
Add a new section named SECTIONNAME while copying the file. The
contents of the new section are taken from the file FILENAME. The
size of the section will be the size of the file. This option only
works on file formats which can support sections with arbitrary
names.
`--rename-section OLDNAME=NEWNAME[,FLAGS]'
Rename a section from OLDNAME to NEWNAME, optionally changing the
section's flags to FLAGS in the process. This has the advantage
over usng a linker script to perform the rename in that the output
stays as an object file and does not become a linked executable.
This option is particularly helpful when the input format is
binary, since this will always create a section called .data. If
for example, you wanted instead to create a section called .rodata
containing binary data you could use the following command line to
achieve it:
xt-objcopy -I binary -O <output_format> -B <architecture> \
--rename-section .data=.rodata,alloc,load,readonly,data,contents \
<input_binary_file> <output_object_file>
`--change-leading-char'
Some object file formats use special characters at the start of
symbols. The most common such character is underscore, which
compilers often add before every symbol. This option tells
`objcopy' to change the leading character of every symbol when it
converts between object file formats. If the object file formats
use the same leading character, this option has no effect.
Otherwise, it will add a character, or remove a character, or
change a character, as appropriate.
`--remove-leading-char'
If the first character of a global symbol is a special symbol
leading character used by the object file format, remove the
character. The most common symbol leading character is
underscore. This option will remove a leading underscore from all
global symbols. This can be useful if you want to link together
objects of different file formats with different conventions for
symbol names. This is different from `--change-leading-char'
because it always changes the symbol name when appropriate,
regardless of the object file format of the output file.
`--reverse-bytes=NUM'
Reverse the bytes in a section with output contents. A section
length must be evenly divisible by the value given in order for
the swap to be able to take place. Reversing takes place before
the interleaving is performed.
This option is used typically in generating ROM images for
problematic target systems. For example, on some target boards,
the 32-bit words fetched from 8-bit ROMs are re-assembled in
little-endian byte order regardless of the CPU byte order.
Depending on the programming model, the endianness of the ROM may
need to be modified.
Consider a simple file with a section containing the following
eight bytes: `12345678'.
Using `--reverse-bytes=2' for the above example, the bytes in the
output file would be ordered `21436587'.
Using `--reverse-bytes=4' for the above example, the bytes in the
output file would be ordered `43218765'.
By using `--reverse-bytes=2' for the above example, followed by
`--reverse-bytes=4' on the output file, the bytes in the second
output file would be ordered `34127856'.
`--srec-len=IVAL'
Meaningful only for srec output. Set the maximum length of the
Srecords being produced to IVAL. This length covers both address,
data and crc fields.
`--srec-forceS3'
Meaningful only for srec output. Avoid generation of S1/S2
records, creating S3-only record format.
`--redefine-sym OLD=NEW'
Change the name of a symbol OLD, to NEW. This can be useful when
one is trying link two things together for which you have no
source, and there are name collisions.
`--redefine-syms=FILENAME'
Apply `--redefine-sym' to each symbol pair "OLD NEW" listed in the
file FILENAME. FILENAME is simply a flat file, with one symbol
pair per line. Line comments may be introduced by the hash
character. This option may be given more than once.
`--weaken'
Change all global symbols in the file to be weak. This can be
useful when building an object which will be linked against other
objects using the `-R' option to the linker. This option is only
effective when using an object file format which supports weak
symbols.
`--keep-symbols=FILENAME'
Apply `--keep-symbol' option to each symbol listed in the file
FILENAME. FILENAME is simply a flat file, with one symbol name
per line. Line comments may be introduced by the hash character.
This option may be given more than once.
`--strip-symbols=FILENAME'
Apply `--strip-symbol' option to each symbol listed in the file
FILENAME. FILENAME is simply a flat file, with one symbol name
per line. Line comments may be introduced by the hash character.
This option may be given more than once.
`--strip-unneeded-symbols=FILENAME'
Apply `--strip-unneeded-symbol' option to each symbol listed in
the file FILENAME. FILENAME is simply a flat file, with one
symbol name per line. Line comments may be introduced by the hash
character. This option may be given more than once.
`--keep-global-symbols=FILENAME'
Apply `--keep-global-symbol' option to each symbol listed in the
file FILENAME. FILENAME is simply a flat file, with one symbol
name per line. Line comments may be introduced by the hash
character. This option may be given more than once.
`--localize-symbols=FILENAME'
Apply `--localize-symbol' option to each symbol listed in the file
FILENAME. FILENAME is simply a flat file, with one symbol name
per line. Line comments may be introduced by the hash character.
This option may be given more than once.
`--globalize-symbols=FILENAME'
Apply `--globalize-symbol' option to each symbol listed in the file
FILENAME. FILENAME is simply a flat file, with one symbol name
per line. Line comments may be introduced by the hash character.
This option may be given more than once.
`--weaken-symbols=FILENAME'
Apply `--weaken-symbol' option to each symbol listed in the file
FILENAME. FILENAME is simply a flat file, with one symbol name
per line. Line comments may be introduced by the hash character.
This option may be given more than once.
`--alt-machine-code=INDEX'
If the output architecture has alternate machine codes, use the
INDEXth code instead of the default one. This is useful in case a
machine is assigned an official code and the tool-chain adopts the
new code, but other applications still depend on the original code
being used. For ELF based architectures if the INDEX alternative
does not exist then the value is treated as an absolute number to
be stored in the e_machine field of the ELF header.
`--writable-text'
Mark the output text as writable. This option isn't meaningful
for all object file formats.
`--readonly-text'
Make the output text write protected. This option isn't
meaningful for all object file formats.
`--pure'
Mark the output file as demand paged. This option isn't
meaningful for all object file formats.
`--impure'
Mark the output file as impure. This option isn't meaningful for
all object file formats.
`--prefix-symbols=STRING'
Prefix all symbols in the output file with STRING.
`--prefix-sections=STRING'
Prefix all section names in the output file with STRING.
`--prefix-alloc-sections=STRING'
Prefix all the names of all allocated sections in the output file
with STRING.
`--add-gnu-debuglink=PATH-TO-FILE'
Creates a .gnu_debuglink section which contains a reference to
PATH-TO-FILE and adds it to the output file.
`--keep-file-symbols'
When stripping a file, perhaps with `--strip-debug' or
`--strip-unneeded', retain any symbols specifying source file
names, which would otherwise get stripped.
`--only-keep-debug'
Strip a file, removing contents of any sections that would not be
stripped by `--strip-debug' and leaving the debugging sections
intact. In ELF files, this preserves all note sections in the
output.
The intention is that this option will be used in conjunction with
`--add-gnu-debuglink' to create a two part executable. One a
stripped binary which will occupy less space in RAM and in a
distribution and the second a debugging information file which is
only needed if debugging abilities are required. The suggested
procedure to create these files is as follows:
1. Link the executable as normal. Assuming that is is called
`foo' then...
2. Run `xt-objcopy --only-keep-debug foo foo.dbg' to create a
file containing the debugging info.
3. Run `xt-objcopy --strip-debug foo' to create a stripped
executable.
4. Run `xt-objcopy --add-gnu-debuglink=foo.dbg foo' to add a
link to the debugging info into the stripped executable.
Note--the choice of `.dbg' as an extension for the debug info file
is arbitrary. Also the `--only-keep-debug' step is optional. You
could instead do this:
1. Link the executable as normal.
2. Copy `foo' to `foo.full'
3. Run `xt-objcopy --strip-debug foo'
4. Run `xt-objcopy --add-gnu-debuglink=foo.full foo'
i.e., the file pointed to by the `--add-gnu-debuglink' can be the
full executable. It does not have to be a file created by the
`--only-keep-debug' switch.
Note--this switch is only intended for use on fully linked files.
It does not make sense to use it on object files where the
debugging information may be incomplete. Besides the
gnu_debuglink feature currently only supports the presence of one
filename containing debugging information, not multiple filenames
on a one-per-object-file basis.
`--extract-symbol'
Keep the file's section flags and symbols but remove all section
data. Specifically, the option:
* removes the contents of all sections;
* sets the size of every section to zero; and
* sets the file's start address to zero.
This option is used to build a `.sym' file for a VxWorks kernel.
It can also be a useful way of reducing the size of a
`--just-symbols' linker input file.
`--compress-debug-sections'
Compress DWARF debug sections using zlib.
`--decompress-debug-sections'
Decompress DWARF debug sections using zlib.
`--xtensa-core=NAME'
Specify the name of an Xtensa processor core configuration to use.
The configuration information is taken from the entry for NAME in
the Xtensa core registry (see the `--xtensa-system' option). If
this option is not specified, the Xtensa core name is either the
value of the `XTENSA_CORE' environment variable or "default" if
that variable is not set.
`--xtensa-system=REGISTRY'
Specify a directory to be used as the Xtensa core registry. If
this option is not set, the `XTENSA_SYSTEM' environment variable
specifies the Xtensa registry, and if that is not set, the default
registry, `<xtensa_tools_root>/config', is used. Please see the
`Xtensa Software Development Toolkit User's Guide' for more
information about Xtensa core registries.
`--xtensa-params=PATH'
Specify the location of the parameter file in a TIE Development Kit
(TDK) that was produced by running the TIE Compiler (tc). If PATH
identifies a directory rather than a file, the parameters are read
from a file named `default-params' if it exists in that directory.
The parameter file may also be specified by setting the
`XTENSA_PARAMS' environment variable. The `--xtensa-params'
option takes precedence over the environment variable. See the
`Tensilica Instruction Extension (TIE) Language User's Guide' for
more information.
`-V'
`--version'
Show the version number of `objcopy'.
`-v'
`--verbose'
Verbose output: list all object files modified. In the case of
archives, `xt-objcopy -V' lists all members of the archive.
`--help'
Show a summary of the options to `objcopy'.
`--info'
Display a list showing all architectures and object formats
available.

File: binutils.info, Node: objdump, Next: ranlib, Prev: objcopy, Up: Top
4 objdump
*********
xt-objdump [`-a'|`--archive-headers']
[`-b' BFDNAME|`--target=BFDNAME']
[`-C'|`--demangle'[=STYLE] ]
[`-d'|`--disassemble']
[`-D'|`--disassemble-all']
[`-z'|`--disassemble-zeroes']
[`-EB'|`-EL'|`--endian='{big | little }]
[`-f'|`--file-headers']
[`-F'|`--file-offsets']
[`--file-start-context']
[`-g'|`--debugging']
[`-e'|`--debugging-tags']
[`-h'|`--section-headers'|`--headers']
[`-i'|`--info']
[`-j' SECTION|`--section='SECTION]
[`-l'|`--line-numbers']
[`-S'|`--source']
[`-m' MACHINE|`--architecture='MACHINE]
[`-M' OPTIONS|`--disassembler-options='OPTIONS]
[`-p'|`--private-headers']
[`-P' OPTIONS|`--private='OPTIONS]
[`-r'|`--reloc']
[`-R'|`--dynamic-reloc']
[`-s'|`--full-contents']
[`-W[lLiaprmfFsoRt]'|
`--dwarf'[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges,=pubtypes,=trace_info,=trace_abbrev,=trace_aranges,=gdb_index]]
[`-G'|`--stabs']
[`-t'|`--syms']
[`-T'|`--dynamic-syms']
[`-x'|`--all-headers']
[`-w'|`--wide']
[`--start-address='ADDRESS]
[`--stop-address='ADDRESS]
[`--prefix-addresses']
[`--[no-]show-raw-insn']
[`--adjust-vma='OFFSET]
[`--special-syms']
[`--prefix='PREFIX]
[`--prefix-strip='LEVEL]
[`--insn-width='WIDTH]
[`--xtensa-core='NAME]
[`--xtensa-system='REGISTRY]
[`--xtensa-params='PATH]
[`--show-only-insns']
[`--dump-insn-tables']
[`-V'|`--version']
[`-H'|`--help']
OBJFILE...
`objdump' displays information about one or more object files. The
options control what particular information to display. This
information is mostly useful to programmers who are working on the
compilation tools, as opposed to programmers who just want their
program to compile and work.
OBJFILE... are the object files to be examined. When you specify
archives, `objdump' shows information on each of the member object
files.
The long and short forms of options, shown here as alternatives, are
equivalent. At least one option from the list
`-a,-d,-D,-e,-f,-g,-G,-h,-H,-p,-P,-r,-R,-s,-S,-t,-T,-V,-x' must be
given.
`-a'
`--archive-header'
If any of the OBJFILE files are archives, display the archive
header information (in a format similar to `ls -l'). Besides the
information you could list with `xt-ar tv', `xt-objdump -a' shows
the object file format of each archive member.
`--adjust-vma=OFFSET'
When dumping information, first add OFFSET to all the section
addresses. This is useful if the section addresses do not
correspond to the symbol table, which can happen when putting
sections at particular addresses when using a format which can not
represent section addresses, such as a.out.
`-b BFDNAME'
`--target=BFDNAME'
Specify that the object-code format for the object files is
BFDNAME. This option may not be necessary; OBJDUMP can
automatically recognize many formats.
For example,
xt-objdump -b oasys -m vax -h fu.o
displays summary information from the section headers (`-h') of
`fu.o', which is explicitly identified (`-m') as a VAX object file
in the format produced by Oasys compilers. You can list the
formats available with the `-i' option. *Note Target Selection::,
for more information.
`-C'
`--demangle[=STYLE]'
Decode ("demangle") low-level symbol names into user-level names.
Besides removing any initial underscore prepended by the system,
this makes C++ function names readable. Different compilers have
different mangling styles. The optional demangling style argument
can be used to choose an appropriate demangling style for your
compiler. *Note c++filt::, for more information on demangling.
`-g'
`--debugging'
Display debugging information. This attempts to parse STABS and
IEEE debugging format information stored in the file and print it
out using a C like syntax. If neither of these formats are found
this option falls back on the `-W' option to print any DWARF
information in the file.
`-e'
`--debugging-tags'
Like `-g', but the information is generated in a format compatible
with ctags tool.
`-d'
`--disassemble'
Display the assembler mnemonics for the machine instructions from
OBJFILE. This option only disassembles those sections which are
expected to contain instructions.
`-D'
`--disassemble-all'
Like `-d', but disassemble the contents of all sections, not just
those expected to contain instructions.
`--prefix-addresses'
When disassembling, print the complete address on each line. This
is the older disassembly format.
`-EB'
`-EL'
`--endian={big|little}'
Specify the endianness of the object files. This only affects
disassembly. This can be useful when disassembling a file format
which does not describe endianness information, such as S-records.
`-f'
`--file-headers'
Display summary information from the overall header of each of the
OBJFILE files.
`-F'
`--file-offsets'
When disassembling sections, whenever a symbol is displayed, also
display the file offset of the region of data that is about to be
dumped. If zeroes are being skipped, then when disassembly
resumes, tell the user how many zeroes were skipped and the file
offset of the location from where the disassembly resumes. When
dumping sections, display the file offset of the location from
where the dump starts.
`--file-start-context'
Specify that when displaying interlisted source code/disassembly
(assumes `-S') from a file that has not yet been displayed, extend
the context to the start of the file.
`-h'
`--section-headers'
`--headers'
Display summary information from the section headers of the object
file.
File segments may be relocated to nonstandard addresses, for
example by using the `-Ttext', `-Tdata', or `-Tbss' options to
`ld'. However, some object file formats, such as a.out, do not
store the starting address of the file segments. In those
situations, although `ld' relocates the sections correctly, using
`xt-objdump -h' to list the file section headers cannot show the
correct addresses. Instead, it shows the usual addresses, which
are implicit for the target.
`-H'
`--help'
Print a summary of the options to `objdump' and exit.
`-i'
`--info'
Display a list showing all architectures and object formats
available for specification with `-b' or `-m'.
`-j NAME'
`--section=NAME'
Display information only for section NAME.
`-l'
`--line-numbers'
Label the display (using debugging information) with the filename
and source line numbers corresponding to the object code or relocs
shown. Only useful with `-d', `-D', or `-r'.
`-m MACHINE'
`--architecture=MACHINE'
Specify the architecture to use when disassembling object files.
This can be useful when disassembling object files which do not
describe architecture information, such as S-records. You can
list the available architectures with the `-i' option.
`-M OPTIONS'
`--disassembler-options=OPTIONS'
Pass target specific information to the disassembler. Only
supported on some targets. If it is necessary to specify more
than one disassembler option then multiple `-M' options can be
used or can be placed together into a comma separated list.
`-p'
`--private-headers'
Print information that is specific to the object file format. The
exact information printed depends upon the object file format.
For some object file formats, no additional information is printed.
`-P OPTIONS'
`--private=OPTIONS'
Print information that is specific to the object file format. The
argument OPTIONS is a comma separated list that depends on the
format (the lists of options is displayed with the help).
For XCOFF, the available options are: `header', `aout',
`sections', `syms', `relocs', `lineno', `loader', `except',
`typchk', `traceback' and `toc'.
`-r'
`--reloc'
Print the relocation entries of the file. If used with `-d' or
`-D', the relocations are printed interspersed with the
disassembly.
`-R'
`--dynamic-reloc'
Print the dynamic relocation entries of the file. This is only
meaningful for dynamic objects, such as certain types of shared
libraries. As for `-r', if used with `-d' or `-D', the
relocations are printed interspersed with the disassembly.
`-s'
`--full-contents'
Display the full contents of any sections requested. By default
all non-empty sections are displayed.
`-S'
`--source'
Display source code intermixed with disassembly, if possible.
Implies `-d'.
`--prefix=PREFIX'
Specify PREFIX to add to the absolute paths when used with `-S'.
`--prefix-strip=LEVEL'
Indicate how many initial directory names to strip off the
hardwired absolute paths. It has no effect without
`--prefix='PREFIX.
`--show-raw-insn'
When disassembling instructions, print the instruction in hex as
well as in symbolic form. This is the default except when
`--prefix-addresses' is used.
`--no-show-raw-insn'
When disassembling instructions, do not print the instruction
bytes. This is the default when `--prefix-addresses' is used.
`--insn-width=WIDTH'
Display WIDTH bytes on a single line when disassembling
instructions.
`-W[lLiaprmfFsoRt]'
`--dwarf[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges,=pubtypes,=trace_info,=trace_abbrev,=trace_aranges,=gdb_index]'
Displays the contents of the debug sections in the file, if any are
present. If one of the optional letters or words follows the
switch then only data found in those specific sections will be
dumped.
Note that there is no single letter option to display the content
of trace sections or .gdb_index.
Note: the output from the `=info' option can also be affected by
the options `--dwarf-depth', the `--dwarf-start' and the
`--dwarf-check'.
`--dwarf-depth=N'
Limit the dump of the `.debug_info' section to N children. This
is only useful with `--dwarf=info'. The default is to print all
DIEs; the special value 0 for N will also have this effect.
With a non-zero value for N, DIEs at or deeper than N levels will
not be printed. The range for N is zero-based.
`--dwarf-start=N'
Print only DIEs beginning with the DIE numbered N. This is only
useful with `--dwarf=info'.
If specified, this option will suppress printing of any header
information and all DIEs before the DIE numbered N. Only siblings
and children of the specified DIE will be printed.
This can be used in conjunction with `--dwarf-depth'.
`--dwarf-check'
Enable additional checks for consistency of Dwarf information.
`-G'
`--stabs'
Display the full contents of any sections requested. Display the
contents of the .stab and .stab.index and .stab.excl sections from
an ELF file. This is only useful on systems (such as Solaris 2.0)
in which `.stab' debugging symbol-table entries are carried in an
ELF section. In most other file formats, debugging symbol-table
entries are interleaved with linkage symbols, and are visible in
the `--syms' output.
`--start-address=ADDRESS'
Start displaying data at the specified address. This affects the
output of the `-d', `-r' and `-s' options.
`--stop-address=ADDRESS'
Stop displaying data at the specified address. This affects the
output of the `-d', `-r' and `-s' options.
`-t'
`--syms'
Print the symbol table entries of the file. This is similar to
the information provided by the `nm' program, although the display
format is different. The format of the output depends upon the
format of the file being dumped, but there are two main types.
One looks like this:
[ 4](sec 3)(fl 0x00)(ty 0)(scl 3) (nx 1) 0x00000000 .bss
[ 6](sec 1)(fl 0x00)(ty 0)(scl 2) (nx 0) 0x00000000 fred
where the number inside the square brackets is the number of the
entry in the symbol table, the SEC number is the section number,
the FL value are the symbol's flag bits, the TY number is the
symbol's type, the SCL number is the symbol's storage class and
the NX value is the number of auxilary entries associated with the
symbol. The last two fields are the symbol's value and its name.
The other common output format, usually seen with ELF based files,
looks like this:
00000000 l d .bss 00000000 .bss
00000000 g .text 00000000 fred
Here the first number is the symbol's value (sometimes refered to
as its address). The next field is actually a set of characters
and spaces indicating the flag bits that are set on the symbol.
These characters are described below. Next is the section with
which the symbol is associated or _*ABS*_ if the section is
absolute (ie not connected with any section), or _*UND*_ if the
section is referenced in the file being dumped, but not defined
there.
After the section name comes another field, a number, which for
common symbols is the alignment and for other symbol is the size.
Finally the symbol's name is displayed.
The flag characters are divided into 7 groups as follows:
`l'
`g'
`u'
`!'
The symbol is a local (l), global (g), unique global (u),
neither global nor local (a space) or both global and local
(!). A symbol can be neither local or global for a variety
of reasons, e.g., because it is used for debugging, but it is
probably an indication of a bug if it is ever both local and
global. Unique global symbols are a GNU extension to the
standard set of ELF symbol bindings. For such a symbol the
dynamic linker will make sure that in the entire process
there is just one symbol with this name and type in use.
`w'
The symbol is weak (w) or strong (a space).
`C'
The symbol denotes a constructor (C) or an ordinary symbol (a
space).
`W'
The symbol is a warning (W) or a normal symbol (a space). A
warning symbol's name is a message to be displayed if the
symbol following the warning symbol is ever referenced.
`I'
`i'
The symbol is an indirect reference to another symbol (I), a
function to be evaluated during reloc processing (i) or a
normal symbol (a space).
`d'
`D'
The symbol is a debugging symbol (d) or a dynamic symbol (D)
or a normal symbol (a space).
`F'
`f'
`O'
The symbol is the name of a function (F) or a file (f) or an
object (O) or just a normal symbol (a space).
`-T'
`--dynamic-syms'
Print the dynamic symbol table entries of the file. This is only
meaningful for dynamic objects, such as certain types of shared
libraries. This is similar to the information provided by the `nm'
program when given the `-D' (`--dynamic') option.
`--special-syms'
When displaying symbols include those which the target considers
to be special in some way and which would not normally be of
interest to the user.
`-V'
`--version'
Print the version number of `objdump' and exit.
`-x'
`--all-headers'
Display all available header information, including the symbol
table and relocation entries. Using `-x' is equivalent to
specifying all of `-a -f -h -p -r -t'.
`--xtensa-core=NAME'
Specify the name of an Xtensa processor core configuration to use.
The configuration information is taken from the entry for NAME in
the Xtensa core registry (see the `--xtensa-system' option). If
this option is not specified, the Xtensa core name is either the
value of the `XTENSA_CORE' environment variable or "default" if
that variable is not set.
`--xtensa-system=REGISTRY'
Specify a directory to be used as the Xtensa core registry. If
this option is not set, the `XTENSA_SYSTEM' environment variable
specifies the Xtensa registry, and if that is not set, the default
registry, `<xtensa_tools_root>/config', is used. Please see the
`Xtensa Software Development Toolkit User's Guide' for more
information about Xtensa core registries.
`--xtensa-params=PATH'
Specify the location of the parameter file in a TIE Development Kit
(TDK) that was produced by running the TIE Compiler (tc). If PATH
identifies a directory rather than a file, the parameters are read
from a file named `default-params' if it exists in that directory.
The parameter file may also be specified by setting the
`XTENSA_PARAMS' environment variable. The `--xtensa-params'
option takes precedence over the environment variable. See the
`Tensilica Instruction Extension (TIE) Language User's Guide' for
more information.
`--dump-insn-tables'
For each section that has instruction table entries, print out the
instruction table entries for the section. Instruction table
entries are used to keep track of what parts of an Xtensa object
file were assembled as source instructions.
`--show-only-insns'
When disassembling a section, only display the instructions that
are marked in the instruction tables. If an object file does not
have complete instruction tables, this option has no effect.
`-w'
`--wide'
Format some lines for output devices that have more than 80
columns. Also do not truncate symbol names when they are
displayed.
`-z'
`--disassemble-zeroes'
Normally the disassembly output will skip blocks of zeroes. This
option directs the disassembler to disassemble those blocks, just
like any other data.

File: binutils.info, Node: ranlib, Next: readelf, Prev: objdump, Up: Top
5 ranlib
********
xt-ranlib [`--plugin' NAME] [`-DhHvVt'] ARCHIVE
`ranlib' generates an index to the contents of an archive and stores
it in the archive. The index lists each symbol defined by a member of
an archive that is a relocatable object file.
You may use `xt-nm -s' or `xt-nm --print-armap' to list this index.
An archive with such an index speeds up linking to the library and
allows routines in the library to call each other without regard to
their placement in the archive.
The GNU `ranlib' program is another form of GNU `ar'; running
`xt-ranlib' is completely equivalent to executing `xt-ar -s'. *Note
ar::.
`-h'
`-H'
`--help'
Show usage information for `ranlib'.
`-v'
`-V'
`--version'
Show the version number of `ranlib'.
`-D'
Operate in _deterministic_ mode. The symbol map archive member's
header will show zero for the UID, GID, and timestamp. When this
option is used, multiple runs will produce identical output files.
This is the default unless `binutils' was configured with
`--enable-deterministic-archives'.
`-t'
Update the timestamp of the symbol map of an archive.
`-U'
Do _not_ operate in _deterministic_ mode. This is the inverse of
the `-D' option, above: the archive index will get actual UID,
GID, timestamp, and file mode values.
This is the default unless `binutils' was configured with
`--enable-deterministic-archives'.

File: binutils.info, Node: size, Next: strings, Prev: readelf, Up: Top
6 size
******
xt-size [`-A'|`-B'|`-C'|`--format='COMPATIBILITY]
[`--help']
[`-d'|`-o'|`-x'|`--radix='NUMBER]
[`--common']
[`-t'|`--totals']
[`--target='BFDNAME] [`-V'|`--version']
[OBJFILE...]
The GNU `size' utility lists the section sizes--and the total
size--for each of the object or archive files OBJFILE in its argument
list. By default, one line of output is generated for each object file
or each module in an archive.
OBJFILE... are the object files to be examined. If none are
specified, the file `a.out' will be used.
The command line options have the following meanings:
`-A'
`-B'
`-C'
`--format=COMPATIBILITY'
Using one of these options, you can choose whether the output from
GNU `size' resembles output from System V `size' (using `-A', or
`--format=sysv'), or Berkeley `size' (using `-B', or
`--format=berkeley'). You can also select a special output format
for Xtensa processors using `-C' or `--format=xtensa'. The
default is the one-line format similar to Berkeley's.
Here is an example of the Berkeley (default) format of output from
`size':
$ xt-size --format=Berkeley ranlib size
text data bss dec hex filename
294880 81920 11592 388392 5ed28 ranlib
294880 81920 11888 388688 5ee50 size
This is the same data, but displayed closer to System V
conventions:
$ xt-size --format=SysV ranlib size
ranlib :
section size addr
.text 294880 8192
.data 81920 303104
.bss 11592 385024
Total 388392
size :
section size addr
.text 294880 8192
.data 81920 303104
.bss 11888 385024
Total 388688
The Xtensa format is similar to the Berkeley format except that it
separates `readonly' sections from `text' sections. In addition
it categorizes the space for each of the section types into
`code', `literal' and `other'. Each category is shown on a
separate line in the output, along with a `Total' line for all the
categories combined. For example:
$ xt-size --format=xtensa ranlib size
TYPE text rodata data bss dec hex filename
code 13339 0 0 0 13339 341b ranlib
literal 1592 0 0 0 1592 638 ranlib
other 1756 12471 344 508 15079 3ae7 ranlib
Total 16687 12471 344 508 30010 753a ranlib
code 4107 0 0 0 4107 100b size
literal 832 0 0 0 832 340 size
other 708 5079 392 324 6503 1967 size
Total 5647 5079 392 324 11442 2cb2 size
The `code' category in the Xtensa format includes all the Xtensa
instructions, and the `literal' category includes all the data
known to be literals for `L32R' Xtensa instructions. Space for
anything else, such as program data or padding for alignment, is
shown in the `other' category.
`--help'
Show a summary of acceptable arguments and options.
`-d'
`-o'
`-x'
`--radix=NUMBER'
Using one of these options, you can control whether the size of
each section is given in decimal (`-d', or `--radix=10'); octal
(`-o', or `--radix=8'); or hexadecimal (`-x', or `--radix=16').
In `--radix=NUMBER', only the three values (8, 10, 16) are
supported. The total size is always given in two radices; decimal
and hexadecimal for `-d' or `-x' output, or octal and hexadecimal
if you're using `-o'.
`--common'
Print total size of common symbols in each file. When using
Berkeley format these are included in the bss size.
`-t'
`--totals'
Show totals of all objects listed (Berkeley format listing mode
only).
`--target=BFDNAME'
Specify that the object-code format for OBJFILE is BFDNAME. This
option may not be necessary; `size' can automatically recognize
many formats. *Note Target Selection::, for more information.
`--xtensa-core=NAME'
Specify the name of an Xtensa processor core configuration to use.
The configuration information is taken from the entry for NAME in
the Xtensa core registry (see the `--xtensa-system' option). If
this option is not specified, the Xtensa core name is either the
value of the `XTENSA_CORE' environment variable or "default" if
that variable is not set.
`--xtensa-system=REGISTRY'
Specify a directory to be used as the Xtensa core registry. If
this option is not set, the `XTENSA_SYSTEM' environment variable
specifies the Xtensa registry, and if that is not set, the default
registry, `<xtensa_tools_root>/config', is used. Please see the
`Xtensa Software Development Toolkit User's Guide' for more
information about Xtensa core registries.
`--xtensa-params=PATH'
Specify the location of the parameter file in a TIE Development Kit
(TDK) that was produced by running the TIE Compiler (tc). If PATH
identifies a directory rather than a file, the parameters are read
from a file named `default-params' if it exists in that directory.
The parameter file may also be specified by setting the
`XTENSA_PARAMS' environment variable. The `--xtensa-params'
option takes precedence over the environment variable. See the
`Tensilica Instruction Extension (TIE) Language User's Guide' for
more information.
`-V'
`--version'
Display the version number of `size'.

File: binutils.info, Node: strings, Next: strip, Prev: size, Up: Top
7 strings
*********
xt-strings [`-afov'] [`-'MIN-LEN]
[`-n' MIN-LEN] [`--bytes='MIN-LEN]
[`-t' RADIX] [`--radix='RADIX]
[`-e' ENCODING] [`--encoding='ENCODING]
[`-'] [`--all'] [`--print-file-name']
[`-T' BFDNAME] [`--target='BFDNAME]
[`--help'] [`--version'] FILE...
For each FILE given, GNU `strings' prints the printable character
sequences that are at least 4 characters long (or the number given with
the options below) and are followed by an unprintable character. By
default, it only prints the strings from the initialized and loaded
sections of object files; for other types of files, it prints the
strings from the whole file.
`strings' is mainly useful for determining the contents of non-text
files.
`-a'
`--all'
`-'
Do not scan only the initialized and loaded sections of object
files; scan the whole files.
`-f'
`--print-file-name'
Print the name of the file before each string.
`--help'
Print a summary of the program usage on the standard output and
exit.
`-MIN-LEN'
`-n MIN-LEN'
`--bytes=MIN-LEN'
Print sequences of characters that are at least MIN-LEN characters
long, instead of the default 4.
`-o'
Like `-t o'. Some other versions of `strings' have `-o' act like
`-t d' instead. Since we can not be compatible with both ways, we
simply chose one.
`-t RADIX'
`--radix=RADIX'
Print the offset within the file before each string. The single
character argument specifies the radix of the offset--`o' for
octal, `x' for hexadecimal, or `d' for decimal.
`-e ENCODING'
`--encoding=ENCODING'
Select the character encoding of the strings that are to be found.
Possible values for ENCODING are: `s' = single-7-bit-byte
characters (ASCII, ISO 8859, etc., default), `S' =
single-8-bit-byte characters, `b' = 16-bit bigendian, `l' = 16-bit
littleendian, `B' = 32-bit bigendian, `L' = 32-bit littleendian.
Useful for finding wide character strings. (`l' and `b' apply to,
for example, Unicode UTF-16/UCS-2 encodings).
`-T BFDNAME'
`--target=BFDNAME'
Specify an object code format other than your system's default
format. *Note Target Selection::, for more information.
`-v'
`-V'
`--version'
Print the program version number on the standard output and exit.

File: binutils.info, Node: strip, Next: elfedit, Prev: strings, Up: Top
8 strip
*******
xt-strip [`-F' BFDNAME |`--target='BFDNAME]
[`-I' BFDNAME |`--input-target='BFDNAME]
[`-O' BFDNAME |`--output-target='BFDNAME]
[`-s'|`--strip-all']
[`-S'|`-g'|`-d'|`--strip-debug']
[`--strip-dwo']
[`-K' SYMBOLNAME |`--keep-symbol='SYMBOLNAME]
[`-N' SYMBOLNAME |`--strip-symbol='SYMBOLNAME]
[`-w'|`--wildcard']
[`-x'|`--discard-all'] [`-X' |`--discard-locals']
[`-R' SECTIONNAME |`--remove-section='SECTIONNAME]
[`-o' FILE] [`-p'|`--preserve-dates']
[`-D'|`--enable-deterministic-archives']
[`-U'|`--disable-deterministic-archives']
[`--keep-file-symbols']
[`--only-keep-debug']
[`--xtensa-core='NAME]
[`--xtensa-system='REGISTRY]
[`--xtensa-params='PATH]
[`-v' |`--verbose'] [`-V'|`--version']
[`--help'] [`--info']
OBJFILE...
GNU `strip' discards all symbols from object files OBJFILE. The
list of object files may include archives. At least one object file
must be given.
`strip' modifies the files named in its argument, rather than
writing modified copies under different names.
`-F BFDNAME'
`--target=BFDNAME'
Treat the original OBJFILE as a file with the object code format
BFDNAME, and rewrite it in the same format. *Note Target
Selection::, for more information.
`--help'
Show a summary of the options to `strip' and exit.
`--info'
Display a list showing all architectures and object formats
available.
`-I BFDNAME'
`--input-target=BFDNAME'
Treat the original OBJFILE as a file with the object code format
BFDNAME. *Note Target Selection::, for more information.
`-O BFDNAME'
`--output-target=BFDNAME'
Replace OBJFILE with a file in the output format BFDNAME. *Note
Target Selection::, for more information.
`-R SECTIONNAME'
`--remove-section=SECTIONNAME'
Remove any section named SECTIONNAME from the output file. This
option may be given more than once. Note that using this option
inappropriately may make the output file unusable.
`-s'
`--strip-all'
Remove all symbols.
`-g'
`-S'
`-d'
`--strip-debug'
Remove debugging symbols only.
`--strip-dwo'
Remove the contents of all DWARF .dwo sections, leaving the
remaining debugging sections and all symbols intact. See the
description of this option in the `objcopy' section for more
information.
`--strip-unneeded'
Remove all symbols that are not needed for relocation processing.
`-K SYMBOLNAME'
`--keep-symbol=SYMBOLNAME'
When stripping symbols, keep symbol SYMBOLNAME even if it would
normally be stripped. This option may be given more than once.
`-N SYMBOLNAME'
`--strip-symbol=SYMBOLNAME'
Remove symbol SYMBOLNAME from the source file. This option may be
given more than once, and may be combined with strip options other
than `-K'.
`-o FILE'
Put the stripped output in FILE, rather than replacing the
existing file. When this argument is used, only one OBJFILE
argument may be specified.
`-p'
`--preserve-dates'
Preserve the access and modification dates of the file.
`-D'
`--enable-deterministic-archives'
Operate in _deterministic_ mode. When copying archive members and
writing the archive index, use zero for UIDs, GIDs, timestamps,
and use consistent file modes for all files.
If `binutils' was configured with
`--enable-deterministic-archives', then this mode is on by default.
It can be disabled with the `-U' option, below.
`-U'
`--disable-deterministic-archives'
Do _not_ operate in _deterministic_ mode. This is the inverse of
the `-D' option, above: when copying archive members and writing
the archive index, use their actual UID, GID, timestamp, and file
mode values.
This is the default unless `binutils' was configured with
`--enable-deterministic-archives'.
`-w'
`--wildcard'
Permit regular expressions in SYMBOLNAMEs used in other command
line options. The question mark (?), asterisk (*), backslash (\)
and square brackets ([]) operators can be used anywhere in the
symbol name. If the first character of the symbol name is the
exclamation point (!) then the sense of the switch is reversed for
that symbol. For example:
-w -K !foo -K fo*
would cause strip to only keep symbols that start with the letters
"fo", but to discard the symbol "foo".
`-x'
`--discard-all'
Remove non-global symbols.
`-X'
`--discard-locals'
Remove compiler-generated local symbols. (These usually start
with `L' or `.'.)
`--keep-file-symbols'
When stripping a file, perhaps with `--strip-debug' or
`--strip-unneeded', retain any symbols specifying source file
names, which would otherwise get stripped.
`--only-keep-debug'
Strip a file, removing contents of any sections that would not be
stripped by `--strip-debug' and leaving the debugging sections
intact. In ELF files, this preserves all note sections in the
output.
The intention is that this option will be used in conjunction with
`--add-gnu-debuglink' to create a two part executable. One a
stripped binary which will occupy less space in RAM and in a
distribution and the second a debugging information file which is
only needed if debugging abilities are required. The suggested
procedure to create these files is as follows:
1. Link the executable as normal. Assuming that is is called
`foo' then...
2. Run `xt-objcopy --only-keep-debug foo foo.dbg' to create a
file containing the debugging info.
3. Run `xt-objcopy --strip-debug foo' to create a stripped
executable.
4. Run `xt-objcopy --add-gnu-debuglink=foo.dbg foo' to add a
link to the debugging info into the stripped executable.
Note--the choice of `.dbg' as an extension for the debug info file
is arbitrary. Also the `--only-keep-debug' step is optional. You
could instead do this:
1. Link the executable as normal.
2. Copy `foo' to `foo.full'
3. Run `xt-strip --strip-debug foo'
4. Run `xt-objcopy --add-gnu-debuglink=foo.full foo'
i.e., the file pointed to by the `--add-gnu-debuglink' can be the
full executable. It does not have to be a file created by the
`--only-keep-debug' switch.
Note--this switch is only intended for use on fully linked files.
It does not make sense to use it on object files where the
debugging information may be incomplete. Besides the
gnu_debuglink feature currently only supports the presence of one
filename containing debugging information, not multiple filenames
on a one-per-object-file basis.
`-V'
`--version'
Show the version number for `strip'.
`-v'
`--verbose'
Verbose output: list all object files modified. In the case of
archives, `xt-strip -v' lists all members of the archive.

File: binutils.info, Node: c++filt, Next: addr2line, Prev: elfedit, Up: Top
9 c++filt
*********
xt-c++filt [`-_'|`--strip-underscore']
[`-n'|`--no-strip-underscore']
[`-p'|`--no-params']
[`-t'|`--types']
[`-i'|`--no-verbose']
[`-s' FORMAT|`--format='FORMAT]
[`--help'] [`--version'] [SYMBOL...]
The C++ and Java languages provide function overloading, which means
that you can write many functions with the same name, providing that
each function takes parameters of different types. In order to be able
to distinguish these similarly named functions C++ and Java encode them
into a low-level assembler name which uniquely identifies each
different version. This process is known as "mangling". The `c++filt'
(1) program does the inverse mapping: it decodes ("demangles") low-level
names into user-level names so that they can be read.
Every alphanumeric word (consisting of letters, digits, underscores,
dollars, or periods) seen in the input is a potential mangled name. If
the name decodes into a C++ name, the C++ name replaces the low-level
name in the output, otherwise the original word is output. In this way
you can pass an entire assembler source file, containing mangled names,
through `c++filt' and see the same source file containing demangled
names.
You can also use `c++filt' to decipher individual symbols by passing
them on the command line:
xt-c++filt SYMBOL
If no SYMBOL arguments are given, `c++filt' reads symbol names from
the standard input instead. All the results are printed on the
standard output. The difference between reading names from the command
line versus reading names from the standard input is that command line
arguments are expected to be just mangled names and no checking is
performed to separate them from surrounding text. Thus for example:
c++filt -n _Z1fv
will work and demangle the name to "f()" whereas:
c++filt -n _Z1fv,
will not work. (Note the extra comma at the end of the mangled name
which makes it invalid). This command however will work:
echo _Z1fv, | c++filt -n
and will display "f(),", i.e., the demangled name followed by a
trailing comma. This behaviour is because when the names are read from
the standard input it is expected that they might be part of an
assembler source file where there might be extra, extraneous characters
trailing after a mangled name. For example:
.type _Z1fv, @function
`-_'
`--strip-underscore'
On some systems, both the C and C++ compilers put an underscore in
front of every name. For example, the C name `foo' gets the
low-level name `_foo'. This option removes the initial
underscore. Whether `c++filt' removes the underscore by default
is target dependent.
`-n'
`--no-strip-underscore'
Do not remove the initial underscore.
`-p'
`--no-params'
When demangling the name of a function, do not display the types of
the function's parameters.
`-t'
`--types'
Attempt to demangle types as well as function names. This is
disabled by default since mangled types are normally only used
internally in the compiler, and they can be confused with
non-mangled names. For example, a function called "a" treated as
a mangled type name would be demangled to "signed char".
`-i'
`--no-verbose'
Do not include implementation details (if any) in the demangled
output.
`-s FORMAT'
`--format=FORMAT'
`c++filt' can decode various methods of mangling, used by
different compilers. The argument to this option selects which
method it uses:
`auto'
Automatic selection based on executable (the default method)
`gnu'
the one used by the GNU C++ compiler (g++)
`lucid'
the one used by the Lucid compiler (lcc)
`arm'
the one specified by the C++ Annotated Reference Manual
`hp'
the one used by the HP compiler (aCC)
`edg'
the one used by the EDG compiler
`gnu-v3'
the one used by the GNU C++ compiler (g++) with the V3 ABI.
`java'
the one used by the GNU Java compiler (gcj)
`gnat'
the one used by the GNU Ada compiler (GNAT).
`--help'
Print a summary of the options to `c++filt' and exit.
`--version'
Print the version number of `c++filt' and exit.
_Warning:_ `c++filt' is a new utility, and the details of its user
interface are subject to change in future releases. In particular,
a command-line option may be required in the future to decode a
name passed as an argument on the command line; in other words,
xt-c++filt SYMBOL
may in a future release become
xt-c++filt OPTION SYMBOL
---------- Footnotes ----------
(1) MS-DOS does not allow `+' characters in file names, so on MS-DOS
this program is named `CXXFILT'.

File: binutils.info, Node: addr2line, Next: Common Options, Prev: c++filt, Up: Top
10 addr2line
************
xt-addr2line [`-a'|`--addresses']
[`-b' BFDNAME|`--target='BFDNAME]
[`-C'|`--demangle'[=STYLE]]
[`-e' FILENAME|`--exe='FILENAME]
[`-f'|`--functions'] [`-s'|`--basename']
[`-i'|`--inlines']
[`-p'|`--pretty-print']
[`-j'|`--section='NAME]
[`-H'|`--help'] [`-V'|`--version']
[`--xtensa-core='NAME]
[`--xtensa-system='REGISTRY]
[`--xtensa-params='PATH]
[addr addr ...]
`addr2line' translates addresses into file names and line numbers.
Given an address in an executable or an offset in a section of a
relocatable object, it uses the debugging information to figure out
which file name and line number are associated with it.
The executable or relocatable object to use is specified with the
`-e' option. The default is the file `a.out'. The section in the
relocatable object to use is specified with the `-j' option.
`addr2line' has two modes of operation.
In the first, hexadecimal addresses are specified on the command
line, and `addr2line' displays the file name and line number for each
address.
In the second, `addr2line' reads hexadecimal addresses from standard
input, and prints the file name and line number for each address on
standard output. In this mode, `addr2line' may be used in a pipe to
convert dynamically chosen addresses.
The format of the output is `FILENAME:LINENO'. The file name and
line number for each input address is printed on separate lines.
If the `-f' option is used, then each `FILENAME:LINENO' line is
preceded by `FUNCTIONNAME' which is the name of the function containing
the address.
If the `-i' option is used and the code at the given address is
present there because of inlining by the compiler then the
`{FUNCTIONNAME} FILENAME:LINENO' information for the inlining function
will be displayed afterwards. This continues recursively until there
is no more inlining to report.
If the `-a' option is used then the output is prefixed by the input
address.
If the `-p' option is used then the output for each input address is
displayed on one, possibly quite long, line. If `-p' is not used then
the output is broken up into multiple lines, based on the paragraphs
above.
If the file name or function name can not be determined, `addr2line'
will print two question marks in their place. If the line number can
not be determined, `addr2line' will print 0.
The long and short forms of options, shown here as alternatives, are
equivalent.
`-a'
`--addresses'
Display the address before the function name, file and line number
information. The address is printed with a `0x' prefix to easily
identify it.
`-b BFDNAME'
`--target=BFDNAME'
Specify that the object-code format for the object files is
BFDNAME.
`-C'
`--demangle[=STYLE]'
Decode ("demangle") low-level symbol names into user-level names.
Besides removing any initial underscore prepended by the system,
this makes C++ function names readable. Different compilers have
different mangling styles. The optional demangling style argument
can be used to choose an appropriate demangling style for your
compiler. *Note c++filt::, for more information on demangling.
`-e FILENAME'
`--exe=FILENAME'
Specify the name of the executable for which addresses should be
translated. The default file is `a.out'.
`-f'
`--functions'
Display function names as well as file and line number information.
`-s'
`--basenames'
Display only the base of each file name.
`-i'
`--inlines'
If the address belongs to a function that was inlined, the source
information for all enclosing scopes back to the first non-inlined
function will also be printed. For example, if `main' inlines
`callee1' which inlines `callee2', and address is from `callee2',
the source information for `callee1' and `main' will also be
printed.
`-j'
`--section'
Read offsets relative to the specified section instead of absolute
addresses.
`-p'
`--pretty-print'
Make the output more human friendly: each location are printed on
one line. If option `-i' is specified, lines for all enclosing
scopes are prefixed with `(inlined by)'.
`--xtensa-core=NAME'
Specify the name of an Xtensa processor core configuration to use.
The configuration information is taken from the entry for NAME in
the Xtensa core registry (see the `--xtensa-system' option). If
this option is not specified, the Xtensa core name is either the
value of the `XTENSA_CORE' environment variable or "default" if
that variable is not set.
`--xtensa-system=REGISTRY'
Specify a directory to be used as the Xtensa core registry. If
this option is not set, the `XTENSA_SYSTEM' environment variable
specifies the Xtensa registry, and if that is not set, the default
registry, `<xtensa_tools_root>/config', is used. Please see the
`Xtensa Software Development Toolkit User's Guide' for more
information about Xtensa core registries.
`--xtensa-params=PATH'
Specify the location of the parameter file in a TIE Development Kit
(TDK) that was produced by running the TIE Compiler (tc). If PATH
identifies a directory rather than a file, the parameters are read
from a file named `default-params' if it exists in that directory.
The parameter file may also be specified by setting the
`XTENSA_PARAMS' environment variable. The `--xtensa-params'
option takes precedence over the environment variable. See the
`Tensilica Instruction Extension (TIE) Language User's Guide' for
more information.

File: binutils.info, Node: readelf, Next: size, Prev: ranlib, Up: Top
11 readelf
**********
xt-readelf [`-a'|`--all']
[`-h'|`--file-header']
[`-l'|`--program-headers'|`--segments']
[`-S'|`--section-headers'|`--sections']
[`-g'|`--section-groups']
[`-t'|`--section-details']
[`-e'|`--headers']
[`-s'|`--syms'|`--symbols']
[`--dyn-syms']
[`-n'|`--notes']
[`-r'|`--relocs']
[`-u'|`--unwind']
[`-d'|`--dynamic']
[`-V'|`--version-info']
[`-A'|`--arch-specific']
[`-D'|`--use-dynamic']
[`-x' <number or name>|`--hex-dump='<number or name>]
[`-p' <number or name>|`--string-dump='<number or name>]
[`-R' <number or name>|`--relocated-dump='<number or name>]
[`-c'|`--archive-index']
[`-w[lLiaprmfFsoRt]'|
`--debug-dump'[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges,=pubtypes,=trace_info,=trace_abbrev,=trace_aranges,=gdb_index]]
[`--dwarf-depth=N']
[`--dwarf-start=N']
[`-I'|`--histogram']
[`-v'|`--version']
[`-W'|`--wide']
[`-H'|`--help']
ELFFILE...
`readelf' displays information about one or more ELF format object
files. The options control what particular information to display.
ELFFILE... are the object files to be examined. 32-bit and 64-bit
ELF files are supported, as are archives containing ELF files.
This program performs a similar function to `objdump' but it goes
into more detail and it exists independently of the BFD library, so if
there is a bug in BFD then readelf will not be affected.
The long and short forms of options, shown here as alternatives, are
equivalent. At least one option besides `-v' or `-H' must be given.
`-a'
`--all'
Equivalent to specifying `--file-header', `--program-headers',
`--sections', `--symbols', `--relocs', `--dynamic', `--notes' and
`--version-info'.
`-h'
`--file-header'
Displays the information contained in the ELF header at the start
of the file.
`-l'
`--program-headers'
`--segments'
Displays the information contained in the file's segment headers,
if it has any.
`-S'
`--sections'
`--section-headers'
Displays the information contained in the file's section headers,
if it has any.
`-g'
`--section-groups'
Displays the information contained in the file's section groups,
if it has any.
`-t'
`--section-details'
Displays the detailed section information. Implies `-S'.
`-s'
`--symbols'
`--syms'
Displays the entries in symbol table section of the file, if it
has one.
`--dyn-syms'
Displays the entries in dynamic symbol table section of the file,
if it has one.
`-e'
`--headers'
Display all the headers in the file. Equivalent to `-h -l -S'.
`-n'
`--notes'
Displays the contents of the NOTE segments and/or sections, if any.
`-r'
`--relocs'
Displays the contents of the file's relocation section, if it has
one.
`-u'
`--unwind'
Displays the contents of the file's unwind section, if it has one.
Only the unwind sections for IA64 ELF files, as well as ARM
unwind tables (`.ARM.exidx' / `.ARM.extab') are currently
supported.
`-d'
`--dynamic'
Displays the contents of the file's dynamic section, if it has one.
`-V'
`--version-info'
Displays the contents of the version sections in the file, it they
exist.
`-A'
`--arch-specific'
Displays architecture-specific information in the file, if there
is any.
`-D'
`--use-dynamic'
When displaying symbols, this option makes `readelf' use the
symbol hash tables in the file's dynamic section, rather than the
symbol table sections.
`-x <number or name>'
`--hex-dump=<number or name>'
Displays the contents of the indicated section as a hexadecimal
bytes. A number identifies a particular section by index in the
section table; any other string identifies all sections with that
name in the object file.
`-R <number or name>'
`--relocated-dump=<number or name>'
Displays the contents of the indicated section as a hexadecimal
bytes. A number identifies a particular section by index in the
section table; any other string identifies all sections with that
name in the object file. The contents of the section will be
relocated before they are displayed.
`-p <number or name>'
`--string-dump=<number or name>'
Displays the contents of the indicated section as printable
strings. A number identifies a particular section by index in the
section table; any other string identifies all sections with that
name in the object file.
`-c'
`--archive-index'
Displays the file symbol index infomation contained in the header
part of binary archives. Performs the same function as the `t'
command to `ar', but without using the BFD library. *Note ar::.
`-w[lLiaprmfFsoRt]'
`--debug-dump[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges,=pubtypes,=trace_info,=trace_abbrev,=trace_aranges,=gdb_index]'
Displays the contents of the debug sections in the file, if any are
present. If one of the optional letters or words follows the
switch then only data found in those specific sections will be
dumped.
Note that there is no single letter option to display the content
of trace sections or .gdb_index.
Note: the `=decodedline' option will display the interpreted
contents of a .debug_line section whereas the `=rawline' option
dumps the contents in a raw format.
Note: the `=frames-interp' option will display the interpreted
contents of a .debug_frame section whereas the `=frames' option
dumps the contents in a raw format.
Note: the output from the `=info' option can also be affected by
the options `--dwarf-depth' and `--dwarf-start'.
`--dwarf-depth=N'
Limit the dump of the `.debug_info' section to N children. This
is only useful with `--debug-dump=info'. The default is to print
all DIEs; the special value 0 for N will also have this effect.
With a non-zero value for N, DIEs at or deeper than N levels will
not be printed. The range for N is zero-based.
`--dwarf-start=N'
Print only DIEs beginning with the DIE numbered N. This is only
useful with `--debug-dump=info'.
If specified, this option will suppress printing of any header
information and all DIEs before the DIE numbered N. Only siblings
and children of the specified DIE will be printed.
This can be used in conjunction with `--dwarf-depth'.
`-I'
`--histogram'
Display a histogram of bucket list lengths when displaying the
contents of the symbol tables.
`-v'
`--version'
Display the version number of readelf.
`-W'
`--wide'
Don't break output lines to fit into 80 columns. By default
`readelf' breaks section header and segment listing lines for
64-bit ELF files, so that they fit into 80 columns. This option
causes `readelf' to print each section header resp. each segment
one a single line, which is far more readable on terminals wider
than 80 columns.
`-H'
`--help'
Display the command line options understood by `readelf'.

File: binutils.info, Node: elfedit, Next: c++filt, Prev: strip, Up: Top
12 elfedit
**********
elfedit [`--input-mach='MACHINE]
[`--input-type='TYPE]
[`--input-osabi='OSABI]
`--output-mach='MACHINE
`--output-type='TYPE
`--output-osabi='OSABI
[`-v'|`--version']
[`-h'|`--help']
ELFFILE...
`elfedit' updates the ELF header of ELF files which have the
matching ELF machine and file types. The options control how and which
fields in the ELF header should be updated.
ELFFILE... are the ELF files to be updated. 32-bit and 64-bit ELF
files are supported, as are archives containing ELF files.
The long and short forms of options, shown here as alternatives, are
equivalent. At least one of the `--output-mach', `--output-type' and
`--output-osabi' options must be given.
`--input-mach=MACHINE'
Set the matching input ELF machine type to MACHINE. If
`--input-mach' isn't specified, it will match any ELF machine
types.
The supported ELF machine types are, L1OM, K1OM and X86-64.
`--output-mach=MACHINE'
Change the ELF machine type in the ELF header to MACHINE. The
supported ELF machine types are the same as `--input-mach'.
`--input-type=TYPE'
Set the matching input ELF file type to TYPE. If `--input-type'
isn't specified, it will match any ELF file types.
The supported ELF file types are, REL, EXEC and DYN.
`--output-type=TYPE'
Change the ELF file type in the ELF header to TYPE. The supported
ELF types are the same as `--input-type'.
`--input-osabi=OSABI'
Set the matching input ELF file OSABI to OSABI. If
`--input-osabi' isn't specified, it will match any ELF OSABIs.
The supported ELF OSABIs are, NONE, HPUX, NETBSD, GNU, LINUX
(alias for GNU), SOLARIS, AIX, IRIX, FREEBSD, TRU64, MODESTO,
OPENBSD, OPENVMS, NSK, AROS and FENIXOS.
`--output-osabi=OSABI'
Change the ELF OSABI in the ELF header to OSABI. The supported
ELF OSABI are the same as `--input-osabi'.
`-v'
`--version'
Display the version number of `elfedit'.
`-h'
`--help'
Display the command line options understood by `elfedit'.

File: binutils.info, Node: Common Options, Next: GNU Free Documentation License, Prev: addr2line, Up: Top
13 Common Options
*****************
The following command-line options are supported by all of the programs
described in this manual.
`@FILE'
Read command-line options from FILE. The options read are
inserted in place of the original @FILE option. If FILE does not
exist, or cannot be read, then the option will be treated
literally, and not removed.
Options in FILE are separated by whitespace. A whitespace
character may be included in an option by surrounding the entire
option in either single or double quotes. Any character
(including a backslash) may be included by prefixing the character
to be included with a backslash. The FILE may itself contain
additional @FILE options; any such options will be processed
recursively.
`--help'
Display the command-line options supported by the program.
`--version'
Display the version number of the program.
* Menu:
* Target Selection::
* Architecture Selection::

File: binutils.info, Node: Target Selection, Next: Architecture Selection, Up: Common Options
13.1 Target Selection
=====================
A "target" is an object file format. A given target may be supported
for multiple architectures (*note Architecture Selection::). A target
selection may also have variations for different operating systems or
architectures.
The command to list valid target values is `xt-objdump -i' (the
first column of output contains the relevant information).
`objdump' Target
----------------
Ways to specify:
1. command line option: `-b' or `--target'
2. environment variable `GNUTARGET'
3. deduced from the input file
`objcopy' and `strip' Input Target
----------------------------------
Ways to specify:
1. command line options: `-I' or `--input-target', or `-F' or
`--target'
2. environment variable `GNUTARGET'
3. deduced from the input file
`objcopy' and `strip' Output Target
-----------------------------------
Ways to specify:
1. command line options: `-O' or `--output-target', or `-F' or
`--target'
2. the input target (see "`objcopy' and `strip' Input Target" above)
3. environment variable `GNUTARGET'
4. deduced from the input file
`nm', `size', and `strings' Target
----------------------------------
Ways to specify:
1. command line option: `--target'
2. environment variable `GNUTARGET'
3. deduced from the input file

File: binutils.info, Node: Architecture Selection, Prev: Target Selection, Up: Common Options
13.2 Architecture Selection
===========================
An "architecture" is a type of CPU on which an object file is to run.
Its name may contain a colon, separating the name of the processor
family from the name of the particular CPU.
The command to list valid architecture values is `xt-objdump -i' (the
second column contains the relevant information).
`objdump' Architecture
----------------------
Ways to specify:
1. command line option: `-m' or `--architecture'
2. deduced from the input file
`objcopy', `nm', `size', `strings' Architecture
-----------------------------------------------
Ways to specify:
1. deduced from the input file

File: binutils.info, Node: GNU Free Documentation License, Next: History, Prev: Common Options, Up: Top
Appendix A GNU Free Documentation License
*****************************************
Version 1.3, 3 November 2008
Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
`http://fsf.org/'
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
0. PREAMBLE
The purpose of this License is to make a manual, textbook, or other
functional and useful document "free" in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or
noncommercially. Secondarily, this License preserves for the
author and publisher a way to get credit for their work, while not
being considered responsible for modifications made by others.
This License is a kind of "copyleft", which means that derivative
works of the document must themselves be free in the same sense.
It complements the GNU General Public License, which is a copyleft
license designed for free software.
We have designed this License in order to use it for manuals for
free software, because free software needs free documentation: a
free program should come with manuals providing the same freedoms
that the software does. But this License is not limited to
software manuals; it can be used for any textual work, regardless
of subject matter or whether it is published as a printed book.
We recommend this License principally for works whose purpose is
instruction or reference.
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium,
that contains a notice placed by the copyright holder saying it
can be distributed under the terms of this License. Such a notice
grants a world-wide, royalty-free license, unlimited in duration,
to use that work under the conditions stated herein. The
"Document", below, refers to any such manual or work. Any member
of the public is a licensee, and is addressed as "you". You
accept the license if you copy, modify or distribute the work in a
way requiring permission under copyright law.
A "Modified Version" of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section
of the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document's overall
subject (or to related matters) and contains nothing that could
fall directly within that overall subject. (Thus, if the Document
is in part a textbook of mathematics, a Secondary Section may not
explain any mathematics.) The relationship could be a matter of
historical connection with the subject or with related matters, or
of legal, commercial, philosophical, ethical or political position
regarding them.
The "Invariant Sections" are certain Secondary Sections whose
titles are designated, as being those of Invariant Sections, in
the notice that says that the Document is released under this
License. If a section does not fit the above definition of
Secondary then it is not allowed to be designated as Invariant.
The Document may contain zero Invariant Sections. If the Document
does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are
listed, as Front-Cover Texts or Back-Cover Texts, in the notice
that says that the Document is released under this License. A
Front-Cover Text may be at most 5 words, and a Back-Cover Text may
be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images
composed of pixels) generic paint programs or (for drawings) some
widely available drawing editor, and that is suitable for input to
text formatters or for automatic translation to a variety of
formats suitable for input to text formatters. A copy made in an
otherwise Transparent file format whose markup, or absence of
markup, has been arranged to thwart or discourage subsequent
modification by readers is not Transparent. An image format is
not Transparent if used for any substantial amount of text. A
copy that is not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format,
SGML or XML using a publicly available DTD, and
standard-conforming simple HTML, PostScript or PDF designed for
human modification. Examples of transparent image formats include
PNG, XCF and JPG. Opaque formats include proprietary formats that
can be read and edited only by proprietary word processors, SGML or
XML for which the DTD and/or processing tools are not generally
available, and the machine-generated HTML, PostScript or PDF
produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the
material this License requires to appear in the title page. For
works in formats which do not have any title page as such, "Title
Page" means the text near the most prominent appearance of the
work's title, preceding the beginning of the body of the text.
The "publisher" means any person or entity that distributes copies
of the Document to the public.
A section "Entitled XYZ" means a named subunit of the Document
whose title either is precisely XYZ or contains XYZ in parentheses
following text that translates XYZ in another language. (Here XYZ
stands for a specific section name mentioned below, such as
"Acknowledgements", "Dedications", "Endorsements", or "History".)
To "Preserve the Title" of such a section when you modify the
Document means that it remains a section "Entitled XYZ" according
to this definition.
The Document may include Warranty Disclaimers next to the notice
which states that this License applies to the Document. These
Warranty Disclaimers are considered to be included by reference in
this License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and
has no effect on the meaning of this License.
2. VERBATIM COPYING
You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License
applies to the Document are reproduced in all copies, and that you
add no other conditions whatsoever to those of this License. You
may not use technical measures to obstruct or control the reading
or further copying of the copies you make or distribute. However,
you may accept compensation in exchange for copies. If you
distribute a large enough number of copies you must also follow
the conditions in section 3.
You may also lend copies, under the same conditions stated above,
and you may publicly display copies.
3. COPYING IN QUANTITY
If you publish printed copies (or copies in media that commonly
have printed covers) of the Document, numbering more than 100, and
the Document's license notice requires Cover Texts, you must
enclose the copies in covers that carry, clearly and legibly, all
these Cover Texts: Front-Cover Texts on the front cover, and
Back-Cover Texts on the back cover. Both covers must also clearly
and legibly identify you as the publisher of these copies. The
front cover must present the full title with all words of the
title equally prominent and visible. You may add other material
on the covers in addition. Copying with changes limited to the
covers, as long as they preserve the title of the Document and
satisfy these conditions, can be treated as verbatim copying in
other respects.
If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto
adjacent pages.
If you publish or distribute Opaque copies of the Document
numbering more than 100, you must either include a
machine-readable Transparent copy along with each Opaque copy, or
state in or with each Opaque copy a computer-network location from
which the general network-using public has access to download
using public-standard network protocols a complete Transparent
copy of the Document, free of added material. If you use the
latter option, you must take reasonably prudent steps, when you
begin distribution of Opaque copies in quantity, to ensure that
this Transparent copy will remain thus accessible at the stated
location until at least one year after the last time you
distribute an Opaque copy (directly or through your agents or
retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of
the Document well before redistributing any large number of
copies, to give them a chance to provide you with an updated
version of the Document.
4. MODIFICATIONS
You may copy and distribute a Modified Version of the Document
under the conditions of sections 2 and 3 above, provided that you
release the Modified Version under precisely this License, with
the Modified Version filling the role of the Document, thus
licensing distribution and modification of the Modified Version to
whoever possesses a copy of it. In addition, you must do these
things in the Modified Version:
A. Use in the Title Page (and on the covers, if any) a title
distinct from that of the Document, and from those of
previous versions (which should, if there were any, be listed
in the History section of the Document). You may use the
same title as a previous version if the original publisher of
that version gives permission.
B. List on the Title Page, as authors, one or more persons or
entities responsible for authorship of the modifications in
the Modified Version, together with at least five of the
principal authors of the Document (all of its principal
authors, if it has fewer than five), unless they release you
from this requirement.
C. State on the Title page the name of the publisher of the
Modified Version, as the publisher.
D. Preserve all the copyright notices of the Document.
E. Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
F. Include, immediately after the copyright notices, a license
notice giving the public permission to use the Modified
Version under the terms of this License, in the form shown in
the Addendum below.
G. Preserve in that license notice the full lists of Invariant
Sections and required Cover Texts given in the Document's
license notice.
H. Include an unaltered copy of this License.
I. Preserve the section Entitled "History", Preserve its Title,
and add to it an item stating at least the title, year, new
authors, and publisher of the Modified Version as given on
the Title Page. If there is no section Entitled "History" in
the Document, create one stating the title, year, authors,
and publisher of the Document as given on its Title Page,
then add an item describing the Modified Version as stated in
the previous sentence.
J. Preserve the network location, if any, given in the Document
for public access to a Transparent copy of the Document, and
likewise the network locations given in the Document for
previous versions it was based on. These may be placed in
the "History" section. You may omit a network location for a
work that was published at least four years before the
Document itself, or if the original publisher of the version
it refers to gives permission.
K. For any section Entitled "Acknowledgements" or "Dedications",
Preserve the Title of the section, and preserve in the
section all the substance and tone of each of the contributor
acknowledgements and/or dedications given therein.
L. Preserve all the Invariant Sections of the Document,
unaltered in their text and in their titles. Section numbers
or the equivalent are not considered part of the section
titles.
M. Delete any section Entitled "Endorsements". Such a section
may not be included in the Modified Version.
N. Do not retitle any existing section to be Entitled
"Endorsements" or to conflict in title with any Invariant
Section.
O. Preserve any Warranty Disclaimers.
If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no
material copied from the Document, you may at your option
designate some or all of these sections as invariant. To do this,
add their titles to the list of Invariant Sections in the Modified
Version's license notice. These titles must be distinct from any
other section titles.
You may add a section Entitled "Endorsements", provided it contains
nothing but endorsements of your Modified Version by various
parties--for example, statements of peer review or that the text
has been approved by an organization as the authoritative
definition of a standard.
You may add a passage of up to five words as a Front-Cover Text,
and a passage of up to 25 words as a Back-Cover Text, to the end
of the list of Cover Texts in the Modified Version. Only one
passage of Front-Cover Text and one of Back-Cover Text may be
added by (or through arrangements made by) any one entity. If the
Document already includes a cover text for the same cover,
previously added by you or by arrangement made by the same entity
you are acting on behalf of, you may not add another; but you may
replace the old one, on explicit permission from the previous
publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this
License give permission to use their names for publicity for or to
assert or imply endorsement of any Modified Version.
5. COMBINING DOCUMENTS
You may combine the Document with other documents released under
this License, under the terms defined in section 4 above for
modified versions, provided that you include in the combination
all of the Invariant Sections of all of the original documents,
unmodified, and list them all as Invariant Sections of your
combined work in its license notice, and that you preserve all
their Warranty Disclaimers.
The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a single
copy. If there are multiple Invariant Sections with the same name
but different contents, make the title of each such section unique
by adding at the end of it, in parentheses, the name of the
original author or publisher of that section if known, or else a
unique number. Make the same adjustment to the section titles in
the list of Invariant Sections in the license notice of the
combined work.
In the combination, you must combine any sections Entitled
"History" in the various original documents, forming one section
Entitled "History"; likewise combine any sections Entitled
"Acknowledgements", and any sections Entitled "Dedications". You
must delete all sections Entitled "Endorsements."
6. COLLECTIONS OF DOCUMENTS
You may make a collection consisting of the Document and other
documents released under this License, and replace the individual
copies of this License in the various documents with a single copy
that is included in the collection, provided that you follow the
rules of this License for verbatim copying of each of the
documents in all other respects.
You may extract a single document from such a collection, and
distribute it individually under this License, provided you insert
a copy of this License into the extracted document, and follow
this License in all other respects regarding verbatim copying of
that document.
7. AGGREGATION WITH INDEPENDENT WORKS
A compilation of the Document or its derivatives with other
separate and independent documents or works, in or on a volume of
a storage or distribution medium, is called an "aggregate" if the
copyright resulting from the compilation is not used to limit the
legal rights of the compilation's users beyond what the individual
works permit. When the Document is included in an aggregate, this
License does not apply to the other works in the aggregate which
are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half
of the entire aggregate, the Document's Cover Texts may be placed
on covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic
form. Otherwise they must appear on printed covers that bracket
the whole aggregate.
8. TRANSLATION
Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section
4. Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include
translations of some or all Invariant Sections in addition to the
original versions of these Invariant Sections. You may include a
translation of this License, and all the license notices in the
Document, and any Warranty Disclaimers, provided that you also
include the original English version of this License and the
original versions of those notices and disclaimers. In case of a
disagreement between the translation and the original version of
this License or a notice or disclaimer, the original version will
prevail.
If a section in the Document is Entitled "Acknowledgements",
"Dedications", or "History", the requirement (section 4) to
Preserve its Title (section 1) will typically require changing the
actual title.
9. TERMINATION
You may not copy, modify, sublicense, or distribute the Document
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense, or distribute it is void,
and will automatically terminate your rights under this License.
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly
and finally terminates your license, and (b) permanently, if the
copyright holder fails to notify you of the violation by some
reasonable means prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from
that copyright holder, and you cure the violation prior to 30 days
after your receipt of the notice.
Termination of your rights under this section does not terminate
the licenses of parties who have received copies or rights from
you under this License. If your rights have been terminated and
not permanently reinstated, receipt of a copy of some or all of
the same material does not give you any rights to use it.
10. FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions of
the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
`http://www.gnu.org/copyleft/'.
Each version of the License is given a distinguishing version
number. If the Document specifies that a particular numbered
version of this License "or any later version" applies to it, you
have the option of following the terms and conditions either of
that specified version or of any later version that has been
published (not as a draft) by the Free Software Foundation. If
the Document does not specify a version number of this License,
you may choose any version ever published (not as a draft) by the
Free Software Foundation. If the Document specifies that a proxy
can decide which future versions of this License can be used, that
proxy's public statement of acceptance of a version permanently
authorizes you to choose that version for the Document.
11. RELICENSING
"Massive Multiauthor Collaboration Site" (or "MMC Site") means any
World Wide Web server that publishes copyrightable works and also
provides prominent facilities for anybody to edit those works. A
public wiki that anybody can edit is an example of such a server.
A "Massive Multiauthor Collaboration" (or "MMC") contained in the
site means any set of copyrightable works thus published on the MMC
site.
"CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0
license published by Creative Commons Corporation, a not-for-profit
corporation with a principal place of business in San Francisco,
California, as well as future copyleft versions of that license
published by that same organization.
"Incorporate" means to publish or republish a Document, in whole or
in part, as part of another Document.
An MMC is "eligible for relicensing" if it is licensed under this
License, and if all works that were first published under this
License somewhere other than this MMC, and subsequently
incorporated in whole or in part into the MMC, (1) had no cover
texts or invariant sections, and (2) were thus incorporated prior
to November 1, 2008.
The operator of an MMC Site may republish an MMC contained in the
site under CC-BY-SA on the same site at any time before August 1,
2009, provided the MMC is eligible for relicensing.
ADDENDUM: How to use this License for your documents
====================================================
To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and license
notices just after the title page:
Copyright (C) YEAR YOUR NAME.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
Texts. A copy of the license is included in the section entitled ``GNU
Free Documentation License''.
If you have Invariant Sections, Front-Cover Texts and Back-Cover
Texts, replace the "with...Texts." line with this:
with the Invariant Sections being LIST THEIR TITLES, with
the Front-Cover Texts being LIST, and with the Back-Cover Texts
being LIST.
If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.
If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of
free software license, such as the GNU General Public License, to
permit their use in free software.

File: binutils.info, Node: History, Next: Binutils Index, Prev: GNU Free Documentation License, Up: Top
Appendix B History
******************
The original version of this document, entitled "The GNU Binary
Utilities", was written by Roland H. Pesch, Jeffrey M. Osier, and
Cygnus Support. The version for binutils 2.18 was released in 2007 and
published by the Free Software Foundation.
Tensilica, Inc. changed the title to "GNU Binary Utilities User's
Guide" and modified the document to include features specific to Xtensa
processors. The revised document was published by Tensilica, Inc. on
the date shown in the inside cover page. The TeXinfo source files for
this modified document are available from
`http://www.tensilica.com/gnudocs'.

File: binutils.info, Node: Binutils Index, Prev: History, Up: Top
Index
*****
[index]
* Menu:
* --enable-deterministic-archives <1>: strip. (line 106)
* --enable-deterministic-archives <2>: ranlib. (line 33)
* --enable-deterministic-archives <3>: objcopy. (line 280)
* --enable-deterministic-archives: ar. (line 189)
* .stab: objdump. (line 307)
* Add prefix to absolute paths: objdump. (line 250)
* addr2line: addr2line. (line 6)
* address to file name and line number: addr2line. (line 6)
* all header information, object file: objdump. (line 425)
* ar: ar. (line 6)
* architecture: objdump. (line 198)
* architectures available: objdump. (line 183)
* archive contents: ranlib. (line 6)
* Archive file symbol index information: readelf. (line 155)
* archive headers: objdump. (line 72)
* archives: ar. (line 6)
* c++filt: c++filt. (line 6)
* changing object addresses: objcopy. (line 325)
* changing section address: objcopy. (line 335)
* changing section LMA: objcopy. (line 343)
* changing section VMA: objcopy. (line 356)
* changing start address: objcopy. (line 320)
* collections of files: ar. (line 6)
* contents of archive: ar. (line 135)
* creating archives: ar. (line 183)
* creating thin archive: ar. (line 248)
* cxxfilt: c++filt. (line 14)
* dates in archive: ar. (line 222)
* debug symbols: objdump. (line 272)
* debugging symbols: nm. (line 144)
* deleting from archive: ar. (line 66)
* demangling C++ symbols: c++filt. (line 6)
* demangling in nm: nm. (line 152)
* demangling in objdump <1>: addr2line. (line 81)
* demangling in objdump: objdump. (line 100)
* deterministic archives <1>: strip. (line 106)
* deterministic archives <2>: ranlib. (line 33)
* deterministic archives <3>: objcopy. (line 280)
* deterministic archives: ar. (line 189)
* disassembling object code: objdump. (line 122)
* disassembly architecture: objdump. (line 198)
* disassembly endianness: objdump. (line 138)
* disassembly, with source: objdump. (line 246)
* discarding symbols: strip. (line 6)
* display only instructions: objdump. (line 463)
* DWARF: objdump. (line 272)
* dynamic relocation entries, in object file: objdump. (line 234)
* dynamic symbol table entries, printing: objdump. (line 409)
* dynamic symbols: nm. (line 164)
* ELF dynamic section information: readelf. (line 113)
* ELF dynamic symbol table information: readelf. (line 88)
* ELF file header information: readelf. (line 57)
* ELF file information: readelf. (line 6)
* ELF notes: readelf. (line 97)
* ELF object file format: objdump. (line 307)
* ELF program header information: readelf. (line 63)
* ELF reloc information: readelf. (line 101)
* ELF section group information: readelf. (line 74)
* ELF section information: readelf. (line 69)
* ELF segment information: readelf. (line 63)
* ELF symbol table information: readelf. (line 84)
* ELF version sections informations: readelf. (line 117)
* elfedit: elfedit. (line 6)
* endianness: objdump. (line 138)
* external symbols: nm. (line 176)
* extract from archive: ar. (line 150)
* file name: nm. (line 138)
* header information, all: objdump. (line 425)
* input file name: nm. (line 138)
* instruction tables for Xtensa: objdump. (line 457)
* Instruction width: objdump. (line 267)
* libraries: ar. (line 24)
* listings strings: strings. (line 6)
* machine instructions: objdump. (line 122)
* moving in archive: ar. (line 74)
* name duplication in archive: ar. (line 144)
* name length: ar. (line 17)
* nm: nm. (line 6)
* nm compatibility: nm. (line 148)
* nm format: nm. (line 148)
* not writing archive index: ar. (line 241)
* objdump: objdump. (line 6)
* object code format <1>: addr2line. (line 76)
* object code format <2>: strings. (line 67)
* object code format <3>: size. (line 111)
* object code format <4>: objdump. (line 86)
* object code format: nm. (line 240)
* object file header: objdump. (line 144)
* object file information: objdump. (line 6)
* object file offsets: objdump. (line 149)
* object file sections: objdump. (line 241)
* object formats available: objdump. (line 183)
* operations on archive: ar. (line 62)
* printing from archive: ar. (line 86)
* printing strings: strings. (line 6)
* quick append to archive: ar. (line 94)
* radix for section sizes: size. (line 93)
* ranlib <1>: ranlib. (line 6)
* ranlib: ar. (line 129)
* readelf: readelf. (line 6)
* relative placement in archive: ar. (line 171)
* relocation entries, in object file: objdump. (line 228)
* removing symbols: strip. (line 6)
* repeated names in archive: ar. (line 144)
* replacement in archive: ar. (line 111)
* section addresses in objdump: objdump. (line 78)
* section headers: objdump. (line 165)
* section information: objdump. (line 188)
* section sizes: size. (line 6)
* sections, full contents: objdump. (line 241)
* size: size. (line 6)
* size display format: size. (line 28)
* size number format: size. (line 93)
* sorting symbols: nm. (line 195)
* source code context: objdump. (line 158)
* source disassembly: objdump. (line 246)
* source file name: nm. (line 138)
* source filenames for object files: objdump. (line 192)
* stab: objdump. (line 307)
* start-address: objdump. (line 316)
* stop-address: objdump. (line 320)
* strings: strings. (line 6)
* strings, printing: strings. (line 6)
* strip: strip. (line 6)
* Strip absolute paths: objdump. (line 253)
* symbol index <1>: ranlib. (line 6)
* symbol index: ar. (line 27)
* symbol index, listing: nm. (line 210)
* symbol line numbers: nm. (line 180)
* symbol table entries, printing: objdump. (line 325)
* symbols: nm. (line 6)
* symbols, discarding: strip. (line 6)
* thin archives: ar. (line 39)
* undefined symbols: nm. (line 245)
* unwind information: readelf. (line 106)
* Update ELF header: elfedit. (line 6)
* updating an archive: ar. (line 253)
* version: Top. (line 6)
* VMA in objdump: objdump. (line 78)
* wide output, printing: objdump. (line 469)
* writing archive index: ar. (line 235)
* Xtensa instruction tables: objdump. (line 457)
* Xtensa parameter file <1>: addr2line. (line 138)
* Xtensa parameter file <2>: size. (line 132)
* Xtensa parameter file <3>: objdump. (line 446)
* Xtensa parameter file <4>: objcopy. (line 658)
* Xtensa parameter file: nm. (line 278)

Tag Table:
Node: Top2083
Node: Revisions3594
Node: ar3963
Node: nm15999
Node: objcopy26513
Node: objdump55727
Node: ranlib74458
Node: size75993
Node: strings81951
Node: strip84411
Node: c++filt91629
Ref: c++filt-Footnote-196484
Node: addr2line96590
Node: readelf102488
Node: elfedit110041
Node: Common Options112286
Node: Target Selection113389
Node: Architecture Selection114821
Node: GNU Free Documentation License115584
Node: History140756
Node: Binutils Index141513

End Tag Table
Reference in New Issue View Git Blame Copy Permalink