ld.bfd.1: Some remarks and a patch with editorial changes for this man page
Bjarni Ingi Gislason
bjarniig@simnet.is
Tue Oct 28 02:02:45 GMT 2025
More information about the Binutils mailing list
Tue Oct 28 02:02:45 GMT 2025
- Previous message (by thread): [committed] hppa64: Remove code to generate dot symbols for EPLT relocations
- Next message (by thread): ld.bfd.1: Some remarks and a patch with editorial changes for this man page
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Package: binutils-common
Version: 2.45-8
Severity: minor
Tags: patch
* What led up to the situation?
Checking for defects with a new version
test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=0 -ww -z < "man page"
[Use
grep -n -e ' $' -e '\\~$' -e ' \\f.$' -e ' \\"' <file>
to find (most) trailing spaces.]
["test-groff" is a script in the repository for "groff"; is not shipped]
(local copy and "troff" slightly changed by me).
[The fate of "test-nroff" was decided in groff bug #55941.]
* What was the outcome of this action?
Output from "test-groff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=0 -ww -z ":
troff:<stdin>:322: warning: trailing space in the line
troff:<stdin>:327: warning: trailing space in the line
troff:<stdin>:2557: warning: trailing space in the line
troff:<stdin>:2558: warning: trailing space in the line
troff:<stdin>:2559: warning: trailing space in the line
troff:<stdin>:2560: warning: trailing space in the line
troff:<stdin>:2561: warning: trailing space in the line
troff:<stdin>:2562: warning: trailing space in the line
troff:<stdin>:2563: warning: trailing space in the line
troff:<stdin>:2564: warning: trailing space in the line
troff:<stdin>:2565: warning: trailing space in the line
troff:<stdin>:2968: warning: trailing space in the line
* What outcome did you expect instead?
No output (no warnings).
-.-
General remarks and further material, if a diff-file exist, are in the
attachments.
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.16.12+deb14+1-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
-- no debconf information
-------------- next part --------------
Input file is ld.bfd.1
Output from "mandoc -T lint ld.bfd.1": (shortened list)
64 STYLE: input text line longer than 80 bytes:
4 WARNING: empty block: RS
Find most trailing spaces with:
grep -n -e ' $' -e ' \\f.$' -e ' \\"' <man page>
-.-.
Output from
test-nroff -mandoc -t -ww -z ld.bfd.1: (shortened list)
12 line(s) with a trailing space
Find most trailing spaces with:
grep -n -e ' $' -e ' \\f.$' -e ' \\"' <man page>
-.-.
Show if Pod::Man generated this.
2:.\" Automatically generated by Pod::Man 5.0102 (Pod::Simple 3.45)
Latest version in Debian testing:
This is perl 5, version 40, subversion 1 (v5.40.1) built for x86_64-linux-gnu-thread-multi
(with 48 registered patches, see perl -V for more detail)
-.-.
Remove space characters (whitespace) at the end of lines.
Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".
Number of lines affected is
12
-.-.
Change (or include a "FIXME" paragraph about) misused SI (metric)
numeric prefixes (or names) to the binary ones, like Ki (kibi), Mi
(mebi), Gi (gibi), or Ti (tebi), if indicated.
If the metric prefixes are correct, add the definitions or an
explanation to avoid misunderstanding.
3247:to be used as heap for this program. The default is 1MB reserved, 4K
3498:to be used as stack for this program. The default is 2MB reserved, 4K
3676:when linking for 68K targets.
-.-.
Add a (no-break, "\ " or "\~") space between a number and a unit,
as these are not one entity.
3247:to be used as heap for this program. The default is 1MB reserved, 4K
o3498:to be used as stack for this program. The default is 2MB reserved, 4K
3676:when linking for 68K targets.
3751:file. This involves moving the data areas up to the first possible 8K
-.-.
Use the word (in)valid instead of (il)legal,
if not related to legal matters.
See "www.gnu.org/prep/standards".
Think about translations into other languages!
ld.bfd.1:3510:legal values for \fIwhich\fR are \f(CW\*(C`native\*(C'\fR, \f(CW\*(C`windows\*(C'\fR,
-.-.
Move a full stop (period) and a comma outside of a quoted text, if it is
at the end of the quote and does not end a quoted sentence.
3353:documentation for ld's \f(CW\*(C`\-\-enable\-auto\-import\*(C'\fR for details."
-.-.
Add a "\&" (or a comma (Oxford comma)) after an abbreviation
or use English words
(man-pages(7)).
Abbreviation points should be marked as such and protected against being
interpreted as an end of sentence, if they are not, and that independent
of the current place on the line.
169:(e.g. \fBgcc\fR) then all the linker command-line options should be
3267:driver (e.g. Cygwin gcc) and the executable does not support virtual
3464:for the offending variables (e.g. \fBset_foo()\fR and \fBget_foo()\fR accessor
-.-.
Wrong distance (not two spaces) between sentences in the input file.
Separate the sentences and subordinate clauses; each begins on a new
line. See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").
The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.
Remember coding: Only one command ("sentence") on each (logical) line.
E-mail: Easier to quote exactly the relevant lines.
Generally: Easier to edit the sentence.
Patches: Less unaffected text.
Search for two adjacent words is easier, when they belong to the same line,
and the same phrase.
The amount of space between sentences in the output can then be
controlled with the ".ss" request.
Mark a final abbreviation point as such by suffixing it with "\&".
Some sentences (etc.) do not begin on a new line.
Split (sometimes) lines after a punctuation mark; before a conjunction.
Lines with only one (or two) space(s) between sentences could be split,
so latter sentences begin on a new line.
Use
#!/usr/bin/sh
sed -e '/^\./n' \
-e 's/\([[:alpha:]]\)\. */\1.\n/g' $1
to split lines after a sentence period.
Check result with the difference between the formatted outputs.
See also the attachment "general.bugs"
[List of affected lines removed.]
-.-.
Split lines longer than 80 characters (fill completly
an A4 sized page line on a terminal)
into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.
Add "\:" to split the string for the output, "\<newline>" in the source.
[List of affected lines removed.]
Longest line is number 1509 with 129 characters
\&\f(CW\*(C`_\|_start_SECNAME\*(C'\fR and \f(CW\*(C`_\|_stop_SECNAME\*(C'\fR symbols. \fIvalue\fR must be exactly \fBdefault\fR,
-.-.
Do not use more than two space characters between sentences or (better)
only a new line character.
352:\&\fB0\fR for base 8). For i386 PE, \fIentry\fR
2055:file with \f(CW\*(C`.map\*(C'\fR appended. If however the special character
3413:merely building/linking to a static library. In making the choice
-.-.
Remove unnecessary double font change (e.g., \fR\fI) in a row or (better)
use a two-fonts macro.
[List with affected lines removed.]
-.-.
Add a zero (0) in front of a decimal fraction that begins with a period
(.)
7:.if t .sp .5v
-.-.
Put a parenthetical sentence, phrase on a separate line,
if not part of a code.
See man-pages(7), item "semantic newline".
[List of affected lines removed.]
-.-
SYNOPSIS: put a space on both sides of "[" and "]"
(except at the end of the line)
to increase readability (?)
ld.bfd.1:ld [\fBoptions\fR] \fIobjfile\fR ...
-.-.
Use a character "\(->" instead of plain "->" or "\->".
3379:\& extern_array[1] \-\->
3387:\& extern_array[1] \-\->
3396:\& extern_struct.field \-\->
3397:\& { volatile struct s *t=&extern_struct; t\->field }
3404:\& extern_ll \-\->
-.-.
Only one space character is after a possible end of sentence
(after a punctuation, that can end a sentence).
[List of affected lines removed.]
-.-
Add lines to use the CR font for groff instead of CW.
.if t \{\
. ie \\n(.g .ft CR
. el .ft CW
.\}
11:.ft CW
-.-.
.\" Define a fallback for font CW with
.if \n(.g \{\
. ie t .ftr CW CR
. el .ftr CW R
.\}
[List of affected lines removed.]
-.-.
Add "\&" after an ellipsis, when it does not end a sentence.
3392:is to make the struct itself (or the long long, or the ...) variable:
-.-.
Output from "test-groff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=0 -ww -z ":
troff:<stdin>:322: warning: trailing space in the line
troff:<stdin>:327: warning: trailing space in the line
troff:<stdin>:2557: warning: trailing space in the line
troff:<stdin>:2558: warning: trailing space in the line
troff:<stdin>:2559: warning: trailing space in the line
troff:<stdin>:2560: warning: trailing space in the line
troff:<stdin>:2561: warning: trailing space in the line
troff:<stdin>:2562: warning: trailing space in the line
troff:<stdin>:2563: warning: trailing space in the line
troff:<stdin>:2564: warning: trailing space in the line
troff:<stdin>:2565: warning: trailing space in the line
troff:<stdin>:2968: warning: trailing space in the line
-.-
Spelling (from codespell):
ld.bfd.1:645: remaped ==> remapped
ld.bfd.1:829: complier ==> compiler
ld.bfd.1:946: Thse ==> These, Those, This
ld.bfd.1:2217: targetted ==> targeted
ld.bfd.1:2547: indentify ==> identify
ld.bfd.1:2581: statics ==> statistics
-.-
Additionally:
Shift some text blocks to the left to avoid text getting past the right
margin of an A4 sized paper.
.-.
Change "\& ..." lines to a text block with .RS 4m/.RE block.
-.-
Generally:
Split (sometimes) lines after a punctuation mark; before a conjunction.
-.-
-------------- next part --------------
--- ld.bfd.1 2025-10-27 22:56:43.888270962 +0000
+++ ld.bfd.1.new 2025-10-28 00:27:34.794081215 +0000
@@ -4,7 +4,7 @@
.\" Standard preamble:
.\" ========================================================================
.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
+.if t .sp 0.5v
.if n .sp
..
.de Vb \" Begin verbatim text
@@ -166,7 +166,7 @@ Unique abbreviations of the names of mul
accepted.
.PP
Note\-\-\-if the linker is being invoked indirectly, via a compiler driver
-(e.g. \fBgcc\fR) then all the linker command-line options should be
+(e.g.\& \fBgcc\fR) then all the linker command-line options should be
prefixed by \fB\-Wl,\fR (or whatever is appropriate for the particular
compiler driver) like this:
.PP
@@ -319,12 +319,12 @@ sections are evaluated does not change,
\& mem2 : { *(.data.*); } > MEM2
\& mem3 : { *(.data.*); } > MEM3
\& }
-\&
+\&
\& with input sections:
\& .data.1: size 8
\& .data.2: size 0x10
\& .data.3: size 4
-\&
+\&
\& results in .data.1 affected to mem1, and .data.2 and .data.3
\& affected to mem2, even though .data.3 would fit in mem3.
.Ve
@@ -707,7 +707,9 @@ merging properties in \fIfoo.o\fR, whos
is 0x1, and \fIbar.o\fR, which doesn't have property 0xc0000002.
.Sp
.Vb 1
-\& Updated property 0xc0010001 (0x1) to merge foo.o (0x1) and bar.o (0x1)
+.RS 4m
+Updated property 0xc0010001 (0x1) to merge foo.o (0x1) and bar.o (0x1)
+.RE
.Ve
.Sp
This indicates that property 0xc0010001 value is updated to 0x1 in output
@@ -717,14 +719,14 @@ is 0x1, and \fIbar.o\fR, whose 0xc001000
On some ELF targets, a list of fixups inserted by \fB\-\-relax\fR
.Sp
.Vb 1
-\& foo.o: Adjusting branch at 0x00000008 towards "far" in section .text
+.RS 4m
+foo.o: Adjusting branch at 0x00000008 towards "far" in section .text
+.RE
.Ve
.Sp
This indicates that the branch at 0x00000008 in foo.o, targeting
the symbol "far" in section .text, has been replaced by a trampoline.
.RE
-.RS 4
-.RE
.IP \fB\-\-print\-map\-discarded\fR 4
.IX Item "--print-map-discarded"
.PD 0
@@ -1847,8 +1849,6 @@ larger, but may reduce the amount of CTF
large projects this may speed up opening the CTF and save memory in the CTF
consumer at runtime.
.RE
-.RS 4
-.RE
.IP \fB\-\-no\-define\-common\fR 4
.IX Item "--no-define-common"
This option inhibits the assignment of addresses to common symbols.
@@ -2058,16 +2058,17 @@ output file. Additionally if there are
\&\fI%\fR symbol then \f(CW\*(C`.map\*(C'\fR will no longer be appended.
.Sp
.Vb 10
-\& \-o foo.exe \-Map=bar [Creates ./bar]
-\& \-o ../dir/foo.exe \-Map=bar [Creates ./bar]
-\& \-o foo.exe \-Map=../dir [Creates ../dir/foo.exe.map]
-\& \-o ../dir2/foo.exe \-Map=../dir [Creates ../dir/foo.exe.map]
-\& \-o foo.exe \-Map=% [Creates ./foo.exe.map]
-\& \-o ../dir/foo.exe \-Map=% [Creates ../dir/foo.exe.map]
-\& \-o foo.exe \-Map=%.bar [Creates ./foo.exe.bar]
-\& \-o ../dir/foo.exe \-Map=%.bar [Creates ../dir/foo.exe.bar]
-\& \-o ../dir2/foo.exe \-Map=../dir/% [Creates ../dir/../dir2/foo.exe.map]
-\& \-o ../dir2/foo.exe \-Map=../dir/%.bar [Creates ../dir/../dir2/foo.exe.bar]
+.RS 4n
+\-o foo.exe \-Map=bar [Creates ./bar]
+\-o ../dir/foo.exe \-Map=bar [Creates ./bar]
+\-o foo.exe \-Map=../dir [Creates ../dir/foo.exe.map]
+\-o ../dir2/foo.exe \-Map=../dir [Creates ../dir/foo.exe.map]
+\-o foo.exe \-Map=% [Creates ./foo.exe.map]
+\-o ../dir/foo.exe \-Map=% [Creates ../dir/foo.exe.map]
+\-o foo.exe \-Map=%.bar [Creates ./foo.exe.bar]
+\-o ../dir/foo.exe \-Map=%.bar [Creates ../dir/foo.exe.bar]
+\-o ../dir2/foo.exe \-Map=../dir/% [Creates ../dir/../dir2/foo.exe.map]
+\-o ../dir2/foo.exe \-Map=../dir/%.bar [Creates ../dir/../dir2/foo.exe.bar]
.Ve
.Sp
It is an error to specify more than one \f(CW\*(C`%\*(C'\fR character.
@@ -2136,8 +2137,6 @@ select whichever function is most approp
architecture. This is used, for example, to dynamically select an
appropriate memset function.
.RE
-.RS 4
-.RE
.IP \fB\-\-error\-handling\-script=\fR\fIscriptname\fR 4
.IX Item "--error-handling-script=scriptname"
If this option is provided then the linker will invoke
@@ -2438,10 +2437,10 @@ Then if a section ordering file like thi
This would be equivalent to a linker script like this:
.Sp
.Vb 4
-\& SECTIONS {
-\& .text : { *(.text.first) ; *(.text.z*) ; *(.text.hot) ; *(.text .text.*) }
-\& .data : { foo.o(.data.first) ; *(.data.small) ; *(.data.big) ; *(.data .data.*) }
-\& }
+SECTIONS {
+ .text : { *(.text.first) ; *(.text.z*) ; *(.text.hot) ; *(.text .text.*) }
+ .data : { foo.o(.data.first) ; *(.data.small) ; *(.data.big) ; *(.data .data.*) }
+ }
.Ve
.Sp
The advantage of the section ordering file is that it can be used to
@@ -2551,19 +2550,19 @@ reported.
The extended output looks something like this:
.Sp
.Vb 3
-\& Stats: linker version: (GNU Binutils) 2.44.50.20250401
-\& Stats: linker started: Wed Apr 2 09:36:41 2025
-\& Stats: args: ld \-z norelro \-z nomemory\-seal \-z no\-separate\-code \-o a.out [...]
-\&
-\& Stats: phase cpu time memory user time system time
-\& Stats: name (microsec) (KiB) (seconds) (seconds)
-\& Stats: ALL 390082 217740 0 0
-\& Stats: ctf processing 12 0 0 0
-\& Stats: string merge 1324 0 0 0
-\& Stats: parsing 349 288 0 0
-\& Stats: plugins 1 0 0 0
-\& Stats: processing files 259616 214524 0 0
-\& Stats: write 116493 0 0 0
+Stats: linker version: (GNU Binutils) 2.44.50.20250401
+Stats: linker started: Wed Apr 2 09:36:41 2025
+Stats: args: ld \-z norelro \-z nomemory\-seal \-z no\-separate\-code \-o a.out [...]
+\&
+Stats: phase cpu time memory user time system time
+Stats: name (microsec) (KiB) (seconds) (seconds)
+Stats: ALL 390082 217740 0 0
+Stats: ctf processing 12 0 0 0
+Stats: string merge 1324 0 0 0
+Stats: parsing 349 288 0 0
+Stats: plugins 1 0 0 0
+Stats: processing files 259616 214524 0 0
+Stats: write 116493 0 0 0
.Ve
.IP \fB\-\-no\-stats\fR 4
.IX Item "--no-stats"
@@ -2772,8 +2771,6 @@ encountered in a different order.
\& <file>(<section>): warning: smaller common is here
.Ve
.RE
-.RS 4
-.RE
.IP \fB\-\-warn\-constructors\fR 4
.IX Item "--warn-constructors"
Warn if any global constructors are used. This is only useful for a few
@@ -2965,7 +2962,7 @@ internal references to \fIsymbol\fR are
\& {
\& return 123;
\& }
-\&
+\&
\& int
\& g (void)
\& {
@@ -3244,7 +3241,7 @@ file offsets which are multiples of this
.IX Item "--heap reserve,commit"
.PD
Specify the number of bytes of memory to reserve (and optionally commit)
-to be used as heap for this program. The default is 1MB reserved, 4K
+to be used as heap for this program. The default is 1\ MB reserved, 4\ KB
committed.
[This option is specific to the i386 PE targeted port of the linker]
.IP \fB\-\-kill\-at\fR 4
@@ -3264,7 +3261,7 @@ section of the BOOT.INI. Otherwise, thi
.IX Item "--disable-large-address-aware"
Reverts the effect of a previous \fB\-\-large\-address\-aware\fR option.
This is useful if \fB\-\-large\-address\-aware\fR is always set by the compiler
-driver (e.g. Cygwin gcc) and the executable does not support virtual
+driver (e.g.\& Cygwin gcc) and the executable does not support virtual
addresses greater than 2 gigabytes.
[This option is specific to PE targeted ports of the linker]
.IP "\fB\-\-major\-image\-version\fR \fIvalue\fR" 4
@@ -3389,7 +3386,7 @@ or
.Ve
.Sp
For structs (and most other multiword data types) the only option
-is to make the struct itself (or the long long, or the ...) variable:
+is to make the struct itself (or the long long, or the ...\&) variable:
.Sp
.Vb 3
\& extern struct s extern_struct;
@@ -3461,7 +3458,7 @@ Solution 2:
.Sp
A fourth way to avoid this problem is to re-code your
library to use a functional interface rather than a data interface
-for the offending variables (e.g. \fBset_foo()\fR and \fBget_foo()\fR accessor
+for the offending variables (e.g.\& \fBset_foo()\fR and \fBget_foo()\fR accessor
functions).
.IP \fB\-\-disable\-auto\-import\fR 4
.IX Item "--disable-auto-import"
@@ -3495,7 +3492,7 @@ addresses which are a multiple of this n
.IX Item "--stack reserve,commit"
.PD
Specify the number of bytes of memory to reserve (and optionally commit)
-to be used as stack for this program. The default is 2MB reserved, 4K
+to be used as stack for this program. The default is 2\ MB reserved, 4\ KB
committed.
[This option is specific to the i386 PE targeted port of the linker]
.IP "\fB\-\-subsystem\fR \fIwhich\fR" 4
@@ -3507,7 +3504,7 @@ committed.
.IX Item "--subsystem which:major.minor"
.PD
Specifies the subsystem under which your program will execute. The
-legal values for \fIwhich\fR are \f(CW\*(C`native\*(C'\fR, \f(CW\*(C`windows\*(C'\fR,
+valid values for \fIwhich\fR are \f(CW\*(C`native\*(C'\fR, \f(CW\*(C`windows\*(C'\fR,
\&\f(CW\*(C`console\*(C'\fR, \f(CW\*(C`posix\*(C'\fR, and \f(CW\*(C`xbox\*(C'\fR. You may optionally set
the subsystem version also. Numeric values are also accepted for
\&\fIwhich\fR.
@@ -3673,7 +3670,7 @@ The definition of such region is then us
paging and addresses within the memory window.
.PP
The following options are supported to control handling of GOT generation
-when linking for 68K targets.
+when linking for 68\ KB targets.
.IP \fB\-\-got=\fR\fItype\fR 4
.IX Item "--got=type"
This option tells the linker which GOT generation scheme to use.
@@ -3748,8 +3745,8 @@ from the beginning through 2.11BSD.
Mark the output as \f(CW\*(C`NMAGIC\*(C'\fR (0410) in the \fIa.out\fR header to
indicate that when the output file is executed, the text portion will
be read-only and shareable among all processes executing the same
-file. This involves moving the data areas up to the first possible 8K
-byte page boundary following the end of the text. This option creates
+file. This involves moving the data areas up to the first possible 8\ kilobyte
+page boundary following the end of the text. This option creates
a \fIpure executable\fR format.
.IP \fB\-z\fR 4
.IX Item "-z"
-------------- next part --------------
Any program (person), that produces man pages, should check the output
for defects by using (both groff and nroff)
[gn]roff -mandoc -t -ww -b -z -K utf8 <man page>
To find trailing space use
grep -n -e ' $' -e ' \\f.$' -e ' \\"' <man page>
The same goes for man pages that are used as an input.
-.-
For a style guide use
mandoc -T lint
-.-
For general input conventions consult the man page "nroff(7)" (item
"Input conventions") or the Texinfo manual about the same item.
-.-
Any "autogenerator" should check its products with the above mentioned
'groff', 'mandoc', and additionally with 'nroff ...'.
It should also check its input files for too long (> 80) lines.
This is just a simple quality control measure.
The "autogenerator" may have to be corrected to get a better man page,
the source file may, and any additional file may.
Common defects:
Not removing trailing spaces (in in- and output).
The reason for these trailing spaces should be found and eliminated.
"git" has a "tool" to point out whitespace,
see for example "git-apply(1)" and git-config(1)")
Not beginning each input sentence on a new line.
Line length and patch size should thus be reduced.
The script "reportbug" uses 'quoted-printable' encoding when a line is
longer than 1024 characters in an 'ascii' file.
See man-pages(7), item "semantic newline".
-.-
The difference between the formatted output of the original
and patched file can be seen with:
nroff -mandoc <file1> > <out1>
nroff -mandoc <file2> > <out2>
diff -d -u <out1> <out2>
and for groff, using
\"printf '%s\n%s\n' '.kern 0' '.ss 12 0' | groff -mandoc -Z - \"
instead of 'nroff -mandoc'
Add the option '-t', if the file contains a table.
Read the output from 'diff -d -u ...' with 'less -R' or similar.
-.-.
If 'man' (man-db) is used to check the manual for warnings,
the following must be set:
The option "-warnings=w"
The environmental variable:
export MAN_KEEP_STDERR=yes (or any non-empty value)
or
(produce only warnings):
export MANROFFOPT="-ww -b -z"
export MAN_KEEP_STDERR=yes (or any non-empty value)
-.-
- Previous message (by thread): [committed] hppa64: Remove code to generate dot symbols for EPLT relocations
- Next message (by thread): ld.bfd.1: Some remarks and a patch with editorial changes for this man page
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list