1 \input texinfo @c -*- Texinfo -*-
2 @setfilename binutils.info
8 * Binutils: (binutils).
9 The GNU binary utilities "ar", "ld", "objdump", "nm",
10 "size", "strip", and "ranlib".
17 Copyright @copyright{} 1991 Free Software Foundation, Inc.
19 Permission is granted to make and distribute verbatim copies of
20 this manual provided the copyright notice and this permission notice
21 are preserved on all copies.
24 Permission is granted to process this file through TeX and print the
25 results, provided the printed document carries a copying permission
26 notice identical to this one except for the removal of this paragraph
27 (this paragraph not being relevant to the printed manual).
31 Permission is granted to copy and distribute modified versions of this
32 manual under the conditions for verbatim copying, provided also that
33 the entire resulting derived work is distributed under the terms of a
34 permission notice identical to this one.
36 Permission is granted to copy and distribute translations of this manual
37 into another language, under the above conditions for modified versions.
42 @c This file documents the GNU binary utilities "ar", "ld", "objdump", "nm",
43 @c "size", "strip", and "ranlib".
45 @c Copyright (C) 1991 Free Software Foundation, Inc.
47 @c This text may be freely distributed under the terms of the GNU
48 @c General Public License.
52 @setchapternewpage odd
53 @settitle GNU Binary Utilities
58 @title The GNU Binary Utilities
59 @subtitle Version 1.97
61 @subtitle October 1991
62 @author Roland H. Pesch
63 @author Cygnus Support
67 \def\$#1${{#1}} % Kluge: collect RCS revision info without $...$
68 \xdef\manvers{\$Revision$} % For use in headers, footers too
69 {\parskip=0pt \hfill Cygnus Support\par \hfill \manvers\par \hfill
70 \TeX{}info \texinfoversion\par }
73 @vskip 0pt plus 1filll
74 Copyright @copyright{} 1991 Free Software Foundation, Inc.
76 Permission is granted to make and distribute verbatim copies of
77 this manual provided the copyright notice and this permission notice
78 are preserved on all copies.
80 Permission is granted to copy and distribute modified versions of this
81 manual under the conditions for verbatim copying, provided also that
82 the entire resulting derived work is distributed under the terms of a
83 permission notice identical to this one.
85 Permission is granted to copy and distribute translations of this manual
86 into another language, under the above conditions for modified versions.
89 @node Top, ar, (dir), (dir)
93 This brief manual contains preliminary documentation for the GNU binary
94 utilities (collectively version 1.97):
99 Create, modify, and extract from archives
102 List symbols from object files
105 Display information from object files
108 Generate index to archive contents
111 List section sizes and total size
119 * ar:: Create, modify, and extract from archives
120 * ld:(ld)Overview. Combine object and archive files
121 * nm:: List symbols from object files
122 * objdump:: Display information from object files
123 * ranlib:: Generate index to archive contents
124 * size:: List section sizes and total size
125 * strip:: Discard symbols
129 @node ar, nm, Top, Top
134 @cindex collections of files
136 ar [-]@var{p}@var{mod} [ @var{membername} ] @var{archive} @var{files}@dots{}
137 ar -M [ <mri-script ]
140 The GNU @code{ar} program creates, modifies, and extracts from
141 archives. An @dfn{archive} is a single file holding a collection of
142 other files in a structure that makes it possible to retrieve
143 the original individual files (called @dfn{members} of the archive).
145 The original files' contents, mode (permissions), timestamp, owner, and
146 group are preserved in the archive, and may be reconstituted on
150 GNU @code{ar} can maintain archives whose members have names of any
151 length; however, depending on how @code{ar} is configured on your
152 system, a limit on member-name length may be imposed (for compatibility
153 with archive formats maintained with other tools). If it exists, the
154 limit is often 15 characters (typical of formats related to a.out) or 16
155 characters (typical of formats related to coff).
158 @code{ar} is considered a binary utility because archives of this sort
159 are most often used as @dfn{libraries} holding commonly needed
163 @code{ar} will create an index to the symbols defined in relocatable
164 object modules in the archive when you specify the modifier @samp{s}.
165 Once created, this index is updated in the archive whenever @code{ar}
166 makes a change to its contents (save for the @samp{q} update operation).
167 An archive with such an index speeds up linking to the library, and
168 allows routines in the library to call each other without regard to
169 their placement in the archive.
171 You may use @samp{nm -s} or @samp{nm +print-armap} to list this index
172 table. If an archive lacks the table, another form of @code{ar} called
173 @code{ranlib} can be used to add just the table.
175 @cindex compatibility, @code{ar}
176 @cindex @code{ar} compatibility
177 GNU @code{ar} is designed to be compatible with two different
178 facilities. You can control its activity using command-line options,
179 like the different varieties of @code{ar} on Unix systems; or, if you
180 specify the single command-line option @samp{-M}, you can control it
181 with a script supplied via standard input, like the MRI ``librarian''
185 * ar-cmdline:: Controlling @code{ar} on the command line
186 * ar-scripts:: Controlling @code{ar} with a script
190 @node ar-cmdline, ar-scripts, ar, ar
191 @section Controlling @code{ar} on the command line
194 ar [-]@var{p}@var{mod} [ @var{membername} ] @var{archive} @var{files}@dots{}
197 @cindex Unix compatibility, @code{ar}
198 When you use @code{ar} in the Unix style, @code{ar} insists on at least two
199 arguments to execute: one keyletter specifying the @emph{operation}
200 (optionally accompanied by other keyletters specifying
201 @emph{modifiers}), and the archive name to act on.
203 Most operations can also accept further @var{files} arguments,
204 specifying particular files to operate on.
206 GNU @code{ar} allows you to mix the operation code @var{p} and modifier
207 flags @var{mod} in any order, within the first command-line argument.
209 If you wish, you may begin the first command-line argument with a
212 @cindex operations on archive
213 The @var{p} keyletter specifies what operation to execute; it may be
214 any of the following, but you must specify only one of them:
218 @cindex deleting from archive
219 @emph{Delete} modules from the archive. Specify the names of modules to
220 be deleted as @var{files}; the archive is untouched if you
221 specify no files to delete.
223 If you specify the @samp{v} modifier, @code{ar} will list each module
227 @cindex moving in archive
228 Use this operation to @emph{move} members in an archive.
230 The ordering of members in an archive can make a difference in how
231 programs are linked using the library, if a symbol is defined in more
234 If no modifiers are used with @code{m}, any members you name in the
235 @var{files} arguments are moved to the @emph{end} of the archive;
236 you can use the @samp{a}, @samp{b}, or @samp{i} modifiers to move them to a
237 specified place instead.
240 @cindex printing from archive
241 @emph{Print} the specified members of the archive, to the standard
242 output file. If the @samp{v} modifier is specified, show the member
243 name before copying its contents to standard output.
245 If you specify no @var{files}, all the files in the archive are printed.
248 @cindex quick append to archive
249 @emph{Quick append}; add @var{files} to the end of @var{archive},
250 without checking for replacement.
252 The modifiers @samp{a}, @samp{b}, and @samp{i} do @emph{not} affect this
253 operation; new members are always placed at the end of the archive.
255 The modifier @samp{v} makes @code{ar} list each file as it is appended.
257 Since the point of this operation is speed, the archive's symbol table
258 index is not updated, even if it already existed; you can use @samp{ar s} or
259 @code{ranlib} explicitly to update the symbol table index.
262 @cindex replacement in archive
263 Insert @var{files} into @var{archive} (with @emph{replacement}). This
264 operation differs from @samp{q} in that any previously existing members
265 are deleted if their names match those being added.
267 If one of the files named in @var{files} doesn't exist, @code{ar}
268 displays an error message, and leaves undisturbed any existing members
269 of the archive matching that name.
271 By default, new members are added at the end of the file; but you may
272 use one of the modifiers @samp{a}, @samp{b}, or @samp{i} to request
273 placement relative to some existing member.
275 The modifier @samp{v} used with this operation elicits a line of
276 output for each file inserted, along with one of the letters @samp{a} or
277 @samp{r} to indicate whether the file was appended (no old member
278 deleted) or replaced.
281 @cindex contents of archive
282 Display a @emph{table} listing the contents of @var{archive}, or those
283 of the files listed in @var{files} that are present in the
284 archive. Normally only the member name is shown; if you also want to
285 see the modes (permissions), timestamp, owner, group, and size, you can
286 request that by also specifying the @samp{v} modifier.
288 If you do not specify any @var{files}, all files in the archive
291 @cindex repeated names in archive
292 @cindex name duplication in archive
293 If there is more than one file with the same name (say, @samp{fie}) in
294 an archive (say @samp{b.a}), @samp{ar t b.a fie} will list only the
295 first instance; to see them all, you must ask for a complete
296 listing---in our example, @samp{ar t b.a}.
297 @c WRS only; per Gumby, this is implementation-dependent, and in a more
298 @c recent case in fact works the other way.
301 @cindex extract from archive
302 @emph{Extract} members (named @var{files}) from the archive. You can
303 use the @samp{v} modifier with this operation, to request that
304 @code{ar} list each name as it extracts it.
306 If you do not specify any @var{files}, all files in the archive
311 A number of modifiers (@var{mod}) may immediately follow the @var{p}
312 keyletter, to specify variations on an operation's behavior:
316 @cindex relative placement in archive
317 Add new files @emph{after} an existing member of the
318 archive. If you use the modifier @code{a}, the name of an existing archive
319 member must be present as the @var{membername} argument, before the
320 @var{archive} specification.
323 Add new files @emph{before} an existing member of the
324 archive. If you use the modifier @code{b}, the name of an existing archive
325 member must be present as the @var{membername} argument, before the
326 @var{archive} specification. (same as @samp{i}).
329 @cindex creating archives
330 @emph{Create} the archive. The specified @var{archive} is always
331 created if it didn't exist, when you request an update. But a warning is
332 issued unless you specify in advance that you expect to create it, by
336 Insert new files @emph{before} an existing member of the
337 archive. If you use the modifier @code{i}, the name of an existing archive
338 member must be present as the @var{membername} argument, before the
339 @var{archive} specification. (same as @samp{b}).
342 This modifier is accepted but not used.
343 @c whaffor ar l modifier??? presumably compat; with
344 @c what???---pesch@@cygnus.com, 25jan91
347 @cindex dates in archive
348 Preserve the @emph{original} dates of members when extracting them. If
349 you do not specify this modifier, files extracted from the archive
350 will be stamped with the time of extraction.
353 @cindex writing archive index
354 Write an object-file index into the archive, or update an existing one,
355 even if no other change is made to the archive. You may use this modifier
356 flag either with any operation, or alone. Running @samp{ar s} on an
357 archive is equivalent to running @samp{ranlib} on it.
360 @cindex updating an archive
361 Normally, @code{ar r}@dots{} inserts all files
362 listed into the archive. If you would like to insert @emph{only} those
363 of the files you list that are newer than existing members of the same
364 names, use this modifier. The @samp{u} modifier is allowed only for the
365 operation @samp{r} (replace). In particular, the combination @samp{qu} is
366 not allowed, since checking the timestamps would lose any speed
367 advantage from the operation @samp{q}.
370 This modifier requests the @emph{verbose} version of an operation. Many
371 operations display additional information, such as filenames processed,
372 when the modifier @samp{v} is appended.
375 @node ar-scripts, , ar-cmdline, ar
376 @section Controlling @code{ar} with a script
379 ar -M [ <@var{script} ]
382 @cindex MRI compatibility, @code{ar}
383 @cindex scripts, @code{ar}
384 If you use the single command-line option @samp{-M} with @code{ar}, you
385 can control its operation with a rudimentary command language. This
386 form of @code{ar} will operate interactively if standard input is coming
387 directly from a terminal. During interactive use, @code{ar} prompts for
388 input (the prompt is @samp{AR >}), and continues executing even after
389 errors. If you redirect standard input to a script file, no prompts are
390 issued, and @code{ar} will abandon execution (with a nonzero exit code)
393 The @code{ar} command language is @emph{not} designed to be equivalent
394 to the command-line options; in fact, it provides somewhat less control
395 over archives. The only purpose of the command language is to ease the
396 transition to GNU @code{ar} for developers who already have scripts
397 written for the MRI ``librarian'' program.
399 The syntax for the @code{ar} command language is straightforward:
402 commands are recognized in upper or lower case; for example, @code{LIST}
403 is the same as @code{list}. In the following descriptions, commands are
404 shown in upper case for clarity.
407 a single command may appear on each line; it is the first word on the
411 empty lines are allowed, and have no effect.
414 comments are allowed; text after either of the characters @samp{*}
415 or @samp{;} is ignored.
418 Whenever you use a list of names as part of the argument to an @code{ar}
419 command, you can separate the individual names with either commas or
420 blanks. Commas are shown in the explanations below, for clarity.
423 @samp{+} is used as a line continuation character; if @samp{+} appears
424 at the end of a line, the text on the following line is considered part
425 of the current command.
428 Here are the commands you can use in @code{ar} scripts, or when using
429 @code{ar} interactively. Three of them have special significance:
431 @code{OPEN} or @code{CREATE} specify a @dfn{current archive}, which is
432 a temporary file required for most of the other commands.
434 @code{SAVE} commits the changes so far specified by the script. Prior
435 to @code{SAVE}, commands affect only the temporary copy of the current
439 @item ADDLIB @var{archive}
440 @itemx ADDLIB @var{archive} (@var{module}, @var{module}, @dots{} @var{module})
441 Add all the contents of @var{archive} (or, if specified, each named
442 @var{module} from @var{archive}) to the current archive.
444 Requires prior use of @code{OPEN} or @code{CREATE}.
446 @item ADDMOD @var{file}, @var{file}, @dots{} @var{file}
447 @c FIXME! w/Replacement?? If so, like "ar r @var{archive} @var{names}"
448 @c else like "ar q..."
449 Add each named @var{file} as a module in the current archive.
451 Requires prior use of @code{OPEN} or @code{CREATE}.
454 Discard the contents of the current archive, cancelling the effect of
455 any operations since the last @code{SAVE}. May be executed (with no
456 effect) even if no current archive is specified.
458 @item CREATE @var{archive}
459 Creates an archive, and makes it the current archive (required for many
460 other commands). The new archive is created with a temporary name; it
461 is not actually saved as @var{archive} until you use @code{SAVE}.
462 You can overwrite existing archives; similarly, the contents of any
463 existing file named @var{archive} will not be destroyed until @code{SAVE}.
465 @item DELETE @var{module}, @var{module}, @dots{} @var{module}
466 Delete each listed @var{module} from the current archive; equivalent to
467 @samp{ar -d @var{archive} @var{module} @dots{} @var{module}}.
469 Requires prior use of @code{OPEN} or @code{CREATE}.
471 @item DIRECTORY @var{archive} (@var{module}, @dots{} @var{module})
472 @itemx DIRECTORY @var{archive} (@var{module}, @dots{} @var{module}) @var{outputfile}
473 List each named @var{module} present in @var{archive}. The separate
474 command @code{VERBOSE} specifies the form of the output: when verbose
475 output is off, output is like that of @samp{ar -t @var{archive}
476 @var{module}@dots{}}. When verbose output is on, the listing is like
477 @samp{ar -tv @var{archive} @var{module}@dots{}}.
479 Output normally goes to the standard output stream; however, if you
480 specify @var{outputfile} as a final argument, @code{ar} directs the
484 Exit from @code{ar}, with a @code{0} exit code to indicate successful
485 completion. This command does not save the output file; if you have
486 changed the current archive since the last @code{SAVE} command, those
489 @item EXTRACT @var{module}, @var{module}, @dots{} @var{module}
490 Extract each named @var{module} from the current archive, writing them
491 into the current directory as separate files. Equivalent to @samp{ar -x
492 @var{archive} @var{module}@dots{}}.
494 Requires prior use of @code{OPEN} or @code{CREATE}.
497 @c FIXME Tokens but no commands???
504 Display full contents of the current archive, in ``verbose'' style
505 regardless of the state of @code{VERBOSE}. The effect is like @samp{ar
506 tv @var{archive}}). (This single command is a GNU @code{ld}
507 enhancement, rather than present for MRI compatibility.)
509 Requires prior use of @code{OPEN} or @code{CREATE}.
511 @item OPEN @var{archive}
512 Opens an existing archive for use as the current archive (required for
513 many other commands). Any changes as the result of subsequent commands
514 will not actually affect @var{archive} until you next use @code{SAVE}.
516 @item REPLACE @var{module}, @var{module}, @dots{} @var{module}
517 In the current archive, replace each existing @var{module} (named in
518 the @code{REPLACE} arguments) from files in the current working directory.
519 To execute this command without errors, both the file, and the module in
520 the current archive, must exist.
522 Requires prior use of @code{OPEN} or @code{CREATE}.
525 Toggle an internal flag governing the output from @code{DIRECTORY}.
526 When the flag is on, @code{DIRECTORY} output matches output from
527 @samp{ar -tv @dots{}}.
530 Commit your changes to the current archive, and actually save it as a
531 file with the name specified in the last @code{CREATE} or @code{OPEN}
534 Requires prior use of @code{OPEN} or @code{CREATE}.
543 The GNU linker @code{ld} is now described in a separate manual.
544 @xref{Top,, Overview,, Using LD: the GNU linker}.
547 @node nm, objdump, ar, Top
553 nm [ -a | +debug-syms ] [ -g | +extern-only ]
554 [ -s | +print-armap ] [ -o | +print-file-name ]
555 [ -n | +numeric-sort ] [ -p | +no-sort ]
556 [ -r | +reverse-sort ] [ -u | +undefined-only ]
557 [ +target @var{bfdname} ]
558 [ @var{objfiles}@dots{} ]
561 GNU @code{nm} will list the symbols from object files @var{objfiles}.
563 The long and short forms of options, shown here as alternatives, are
567 @item @var{objfiles}@dots{}
569 Object files whose symbols are to be listed. If no object files are
570 listed as arguments, @code{nm} assumes @samp{a.out}.
574 @cindex debugging symbols
575 Display debugger-only symbols; normally these are not listed.
579 @cindex external symbols
580 Display only external symbols.
584 @cindex sorting symbols
585 Don't bother to sort the symbols in any order; just print them in the
590 Sort symbols numerically by their addresses, not alphabetically by their
595 @cindex symbol index, listing
596 When listing symbols from archive members, include the index: a mapping
597 (stored in the archive by @code{ar} or @code{ranlib}) of what modules
598 contain definitions for what names.
601 @itemx +print-file-name
602 @cindex input file name
604 @cindex source file name
605 Precede each symbol by the name of the input file where it was found,
606 rather than identifying the input file once only before all of its
611 Reverse the sense of the sort (whether numeric or alphabetic); let the
614 @item +target @var{bfdname}
616 @cindex object code format
617 Specify an object code format other than your system's default format.
618 @xref{objdump}, for information on listing available formats.
619 @c FIXME what *does* +target/no arg do?
622 @itemx +undefined-only
623 @cindex external symbols
624 @cindex undefined symbols
625 Display only undefined symbols (those external to each object file).
629 @node objdump, ranlib, nm, Top
632 @cindex object file information
636 objdump [ -a ] [ -b @var{bfdname} ] [ -d ] [ -f ]
637 [ -h | --header ] [ -i ] [ -j @var{section} ] [ -l ]
638 [ -m @var{machine} ] [ -r | --reloc ] [ -s ]
639 [ --stabs ] [ -t | --syms ] [ -x ]
640 @var{objfiles}@dots{}
643 @code{objdump} displays information about one or more object files.
644 The options control what particular information to display. This
645 information is mostly useful to programmers who are working on the
646 compilation tools, as opposed to programmers who just want their
647 program to compile and work.
649 The long and short forms of options, shown here as alternatives, are
653 @item @var{objfiles}@dots{}
654 The object files to be examined. When you specify archives,
655 @code{objdump} shows information on each of the member object files.
659 @cindex archive headers
660 If any files from @var{objfiles} are archives, display the archive
661 header information (in a format similar to @samp{ls -l}). Besides the
662 information you could list with @samp{ar tv}, @samp{objdump -a} shows
663 the object file format of each archive member.
665 @c suggest longname --target or --format or --bfd
666 @item -b @var{bfdname}
667 @cindex object code format
668 You can specify a particular object-code format for your object files as
669 @var{bfdname}. This may not be necessary; @var{objdump} can
670 automatically recognize many formats. For example,
672 objdump -b oasys -m vax -h fu.o
675 Displays summary information from the section headers (@samp{-h}) of
676 @file{fu.o}, which is explicitly identified (@samp{-m}) as a Vax object
677 file in the format produced by Oasys compilers. You can list the
678 formats available with the @samp{-i} option.
681 @cindex disassembling object code
682 @cindex machine instructions
683 Disassemble. Display the assembler mnemonics for the machine
684 instructions from @var{objfiles}.
687 @cindex object file header
688 File header. Display summary information from the overall header of
689 each file in @var{objfiles}.
693 @cindex section headers
694 Header. Display summary information from the section headers of the
698 @cindex architectures available
699 @cindex object formats available
700 Display a list showing all architectures and object formats available
701 for specification with @code{-b} or @code{-m}.
703 @c suggest longname --section
705 @cindex section information
706 Display information only for section @var{name}
708 @c suggest longname --label or --linespec
710 @cindex source filenames for object files
711 Label the display (using debugging information) with the source filename
712 and line numbers corresponding to the object code shown.
714 @c suggest longname --architecture
715 @item -m @var{machine}
717 Specify the object files @var{objfiles} are for architecture
718 @var{machine}. You can list available architectures using the @samp{-i}
723 @cindex relocation entries, in object file
724 Relocation. Print the relocation entries of the file.
727 @cindex sections, full contents
728 @cindex object file sections
729 Display the full contents of any sections requested.
734 @cindex debug symbols
735 @cindex ELF object file format
736 Display the full contents of any sections requested. Display the
737 contents of the .stab and .stab.index and .stab.excl sections from an
738 ELF file. This is only useful on systems (such as Solaris 2.0) in which
739 @code{.stab} debugging symbol-table entries are carried in an ELF
740 section. In most other file formats, debugging symbol-table entries are
741 interleaved with linkage symbols, and are visible in the @samp{--syms}
746 @cindex symbol table entries, printing
747 Symbol Table. Print the symbol table entries of the file.
748 This is similar to the information provided by the @samp{nm} program.
751 @cindex all header information, object file
752 @cindex header information, all
753 Display all available header information, including the symbol table and
754 relocation entries. Using @samp{-x} is equivalent to specifying all of
755 @samp{-a -f -h -r -t}.
759 @node ranlib, size, objdump, Top
763 @cindex archive contents
770 @code{ranlib} generates an index to the contents of an archive, and
771 stores it in the archive. The index lists each symbol defined by a
772 member of an archive that is a relocatable object file.
774 You may use @samp{nm -s} or @samp{nm +print-armap} to list this index.
776 An archive with such an index speeds up linking to the library, and
777 allows routines in the library to call each other without regard to
778 their placement in the archive.
780 The GNU @code{ranlib} program is another form of GNU @code{ar}; running
781 @code{ranlib} is completely equivalent to executing @samp{ar -s}.
784 @node size, strip, ranlib, Top
788 @cindex section sizes
791 size [ -A | -B | +format @var{compatibility} ]
792 [ +help ] [ -d | -o | -x | +radix @var{number} ]
793 [ +target @var{bfdname} ] [ -V | +version ]
794 @var{objfiles}@dots{}
797 The GNU @code{size} utility lists the section sizes---and the total
798 size---for each of the object files @var{objfiles} in its argument list.
799 By default, one line of output is generated for each object file or each
800 module in an archive.
802 The command line options have the following meanings:
804 @item @var{objfiles}@dots{}
805 The object files to be examined.
809 @itemx +format @var{compatibility}
810 @cindex size display format
811 Using one of these options, you can choose whether the output from GNU
812 @code{size} resembles output from System V @code{size} (using @samp{-A},
813 or @samp{+format sysv}), or Berkeley @code{size} (using @samp{-B}, or
814 @samp{+format berkeley}). The default is the one-line format similar to
816 @c Bonus for doc-source readers: you can also say +format=strange (or
817 @c anything else that starts with 's') for sysv, and +format=boring (or
818 @c anything else that starts with 'b') for Berkeley.
820 Here is an example of the Berkeley (default) format of output from
823 eg$ size +format Berkeley ranlib size
824 text data bss dec hex filename
825 294880 81920 11592 388392 5ed28 ranlib
826 294880 81920 11888 388688 5ee50 size
830 This is the same data, but displayed closer to System V conventions:
833 eg$ size +format SysV ranlib size
851 Show a summary of acceptable arguments and options.
856 @itemx +radix @var{number}
857 @cindex size number format
858 @cindex radix for section sizes
859 Using one of these options, you can control whether the size of each
860 section is given in decimal (@samp{-d}, or @samp{+radix 10}); octal
861 (@samp{-o}, or @samp{+radix 8}); or hexadecimal (@samp{-x}, or
862 @samp{+radix 16}). In @samp{+radix @var{number}}, only the three
863 values (8, 10, 16) are supported. The total size is always given in two
864 radices; decimal and hexadecimal for @samp{-d} or @samp{-x} output, or
865 octal and hexadecimal if you're using @samp{-o}.
867 @item +target @var{bfdname}
868 @cindex object code format
869 You can specify a particular object-code format for @var{objfiles} as
870 @var{bfdname}. This may not be necessary; @var{size} can
871 automatically recognize many formats. @xref{objdump}, for information
872 on listing available formats.
876 Display version number information on @code{size} itself.
880 @node strip, Index, size, Top
884 @cindex removing symbols
885 @cindex discarding symbols
888 strip [ -s | +strip-all ] [ -g | -S | +strip-debug ]
889 [ -x | +discard-all ] [ -X | +discard-locals ]
891 @var{objfiles}@dots{}
894 GNU @code{strip} will discard all symbols from object files
895 @var{objfiles}, if no options are specified; or only certain symbols,
896 depending on its command-line options.
898 @code{strip} will not execute unless at least one object file is listed.
901 @emph{WARNING:} @code{strip} modifies the files named in its argument,
902 rather than writing modified copies under different names.
905 The long and short forms of options, shown here as alternatives, are
911 @cindex all symbols, discarding
912 This is the default case: strip all symbol entries from @var{objfiles}.
917 @cindex debugging symbols, discarding
918 Discard only debugging symbol information from @var{objfiles}.
922 @cindex local symbols, discarding
923 Discard all symbols local to each file in @var{objfiles}.
924 @emph{WARNING:} Note that @code{+discard-all} discards only @emph{local}
925 symbols, in spite of its name.
928 @itemx +discard-locals
929 Discard local symbols starting with @samp{L} from each file in
930 @var{objfiles}. (Some compilers produce internally-used symbols that
931 begin with @samp{L}.)
933 @item -T @var{bfdname}
934 @cindex object code format
935 You can specify a particular object-code format @var{bfdname} for
936 @var{objfiles}. This may not be necessary; @var{strip} can automatically
937 recognize many formats. @xref{objdump}, for information on listing
941 @node Index, , strip, Top