From b45619c047b9bcea43bebfd63d2489301262b481 Mon Sep 17 00:00:00 2001 From: Nick Clifton Date: Mon, 24 Jul 2006 13:49:50 +0000 Subject: [PATCH] Fix spelling typos --- bfd/doc/ChangeLog | 5 +++++ bfd/doc/bfd.texinfo | 10 +++++----- bfd/doc/bfdint.texi | 8 ++++---- binutils/ChangeLog | 4 ++++ binutils/doc/binutils.texi | 22 +++++++++++----------- gas/ChangeLog | 9 +++++++++ gas/doc/all.texi | 2 +- gas/doc/as.texinfo | 26 +++++++++++++------------- gas/doc/c-arc.texi | 4 ++-- gas/doc/c-arm.texi | 4 ++-- gas/doc/c-avr.texi | 2 +- gas/doc/c-bfin.texi | 4 ++-- gas/doc/c-i386.texi | 4 ++-- gas/doc/c-i960.texi | 2 +- gas/doc/c-m32r.texi | 16 ++++++++-------- gas/doc/c-m68k.texi | 10 +++++----- gas/doc/c-mmix.texi | 2 +- gas/doc/c-pdp11.texi | 2 +- gas/doc/c-ppc.texi | 4 ++-- gas/doc/c-tic54x.texi | 6 +++--- gas/doc/c-v850.texi | 2 +- gas/doc/c-xtensa.texi | 4 ++-- gas/doc/c-z80.texi | 12 ++++++------ gas/doc/internals.texi | 6 +++--- gprof/ChangeLog | 4 ++++ gprof/gprof.texi | 10 +++++----- ld/ChangeLog | 5 +++++ ld/ld.texinfo | 26 +++++++++++++------------- ld/ldint.texinfo | 10 +++++----- 29 files changed, 126 insertions(+), 99 deletions(-) diff --git a/bfd/doc/ChangeLog b/bfd/doc/ChangeLog index 5ecfab3164d..e41ddf52e85 100644 --- a/bfd/doc/ChangeLog +++ b/bfd/doc/ChangeLog @@ -1,3 +1,8 @@ +2006-07-24 Ralk Wildenhues + + * bfd..texinfo: Fix spelling mistakes. + * bfdint.texinfo: Likewise. + 2006-07-18 Nigel Stephens * bfd.texinfo: Add @section for "What to Put Where". diff --git a/bfd/doc/bfd.texinfo b/bfd/doc/bfd.texinfo index 38ba8ccc81e..dfcebb1e289 100644 --- a/bfd/doc/bfd.texinfo +++ b/bfd/doc/bfd.texinfo @@ -1,7 +1,7 @@ \input texinfo.tex @setfilename bfd.info @c Copyright 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1997, 2000, -@c 2001, 2002, 2003 +@c 2001, 2002, 2003, 2006 @c Free Software Foundation, Inc. @c @synindex fn cp @@ -17,7 +17,7 @@ END-INFO-DIR-ENTRY @ifinfo This file documents the BFD library. -Copyright (C) 1991, 2000, 2001, 2003 Free Software Foundation, Inc. +Copyright (C) 1991, 2000, 2001, 2003, 2006 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 @@ -43,7 +43,7 @@ notice identical to this one except for the removal of this paragraph @title{libbfd} @subtitle{The Binary File Descriptor Library} @sp 1 -@subtitle First Edition---BFD version < 3.0 % Since no product is stable berfore version 3.0 :-) +@subtitle First Edition---BFD version < 3.0 % Since no product is stable before version 3.0 :-) @subtitle Original Document Created: April 1991 @author {Steve Chamberlain} @author {Cygnus Support} @@ -62,7 +62,7 @@ notice identical to this one except for the removal of this paragraph @end tex @vskip 0pt plus 1filll -Copyright @copyright{} 1991, 2001, 2003 Free Software Foundation, Inc. +Copyright @copyright{} 1991, 2001, 2003, 2006 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 @@ -144,7 +144,7 @@ To use the library, include @file{bfd.h} and link with @file{libbfd.a}. BFD provides a common interface to the parts of an object file for a calling application. -When an application sucessfully opens a target file (object, archive, or +When an application successfully opens a target file (object, archive, or whatever), a pointer to an internal structure is returned. This pointer points to a structure called @code{bfd}, described in @file{bfd.h}. Our convention is to call this pointer a BFD, and diff --git a/bfd/doc/bfdint.texi b/bfd/doc/bfdint.texi index 79813decc77..15a763c40f0 100644 --- a/bfd/doc/bfdint.texi +++ b/bfd/doc/bfdint.texi @@ -1,6 +1,6 @@ \input texinfo @c Copyright 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1998, -@c 2000, 2001, 2002, 2003, 2004 +@c 2000, 2001, 2002, 2003, 2004, 2006 @c Free Software Foundation, Inc. @setfilename bfdint.info @@ -189,7 +189,7 @@ and handle it using the special hooks. In some cases there is also implicit information which BFD can not represent. For example, the MIPS processor distinguishes small and -large symbols, and requires that all small symbls be within 32K of the +large symbols, and requires that all small symbols be within 32K of the GP register. This means that the MIPS assembler must be able to mark variables as either small or large, and the MIPS linker must know to put small symbols within range of the GP register. Since BFD can not @@ -230,7 +230,7 @@ Follow the GNU coding standards. Avoid global variables. We ideally want BFD to be fully reentrant, so that it can be used in multiple threads. All uses of global or static variables interfere with that. Initialized constant variables are OK, -and they should be explicitly marked with const. Instead of global +and they should be explicitly marked with @samp{const}. Instead of global variables, use data attached to a BFD or to a linker hash table. @item @@ -1391,7 +1391,7 @@ constants used by the generic support. @subsection ELF sections and segments The ELF ABI permits a file to have either sections or segments or both. -Relocateable object files conventionally have only sections. +Relocatable object files conventionally have only sections. Executables conventionally have both. Core files conventionally have only program segments. diff --git a/binutils/ChangeLog b/binutils/ChangeLog index 8508a18c8ab..a899ca8872d 100644 --- a/binutils/ChangeLog +++ b/binutils/ChangeLog @@ -1,3 +1,7 @@ +2006-07-24 Ralk Wildenhues + + * doc/binutils.texinfo: Fix spelling mistakes. + 2006-07-10 Jakub Jelinek * readelf.c (get_dynamic_type): Handle DT_GNU_HASH. diff --git a/binutils/doc/binutils.texi b/binutils/doc/binutils.texi index de7aaf377ff..d74be80a9ed 100644 --- a/binutils/doc/binutils.texi +++ b/binutils/doc/binutils.texi @@ -889,7 +889,7 @@ 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 transistions between ARM code, THUMB code and +symbols used to mark transitions between ARM code, THUMB code and data. @item -t @var{radix} @@ -1478,7 +1478,7 @@ optional. You could instead do this: @item Run @code{objcopy --add-gnu-debuglink=foo.full foo} @end enumerate -i.e. the file pointed to by the @option{--add-gnu-debuglink} can be the +i.e., the file pointed to by the @option{--add-gnu-debuglink} can be the full executable. It does not have to be a file created by the @option{--only-keep-debug} switch. @@ -1766,15 +1766,15 @@ disassembly of BookE instructions. @option{32} and @option{64} select PowerPC and PowerPC64 disassembly, respectively. @option{e300} selects disassembly for the e300 family. -For MIPS, this option controls the printing of instruction mneumonic +For MIPS, this option controls the printing of instruction mnemonic names and register names in disassembled instructions. Multiple selections from the following may be specified as a comma separated string, and invalid options are ignored: @table @code @item no-aliases -Print the 'raw' instruction mneumonic instead of some pseudo -instruction mneumonic. I.E. print 'daddu' or 'or' instead of 'move', +Print the 'raw' instruction mnemonic instead of some pseudo +instruction mnemonic. I.e., print 'daddu' or 'or' instead of 'move', 'sll' instead of 'nop', etc. @item gpr-names=@var{ABI} @@ -1817,7 +1817,7 @@ For VAX, you can specify function entry addresses with @option{-M entry:0xf00ba}. You can use this multiple times to properly disassemble VAX binary files that don't contain symbol tables (like ROM dumps). In these cases, the function entry mask would otherwise -be decoded as VAX instructions, which would probably lead the the rest +be decoded as VAX instructions, which would probably lead the rest of the function being wrongly disassembled. @item -p @@ -2464,7 +2464,7 @@ 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 seperate them from surrounding text. Thus +checking is performed to separate them from surrounding text. Thus for example: @smallexample @@ -2578,7 +2578,7 @@ the Info entries for @file{binutils}. @quotation @emph{Warning:} @command{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 the future to decode a name +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, @example @@ -2892,7 +2892,7 @@ The name of the output file. If this option is not used, then for the input file name, as the output file name. If there is no non-option argument, then @command{windres} will write to standard output. @command{windres} can not write a COFF file to standard output. Note, -for compatability with @command{rc} the option @option{-fo} is also +for compatibility with @command{rc} the option @option{-fo} is also accepted, but its use is not recommended. @item -J @var{format} @@ -2929,7 +2929,7 @@ Specify an include directory to use when reading an @code{rc} file. @command{windres} will pass this to the preprocessor as an @option{-I} option. @command{windres} will also search this directory when looking for files named in the @code{rc} file. If the argument passed to this command -matches any of the supported @var{formats} (as descrived in the @option{-J} +matches any of the supported @var{formats} (as described in the @option{-J} option), it will issue a deprecation warning, and behave just like the @option{-J} option. New programs should not use this behaviour. If a directory happens to match a @var{format}, simple prefix it with @samp{./} @@ -3837,7 +3837,7 @@ a chance to make a mistake. Even if the problem you experience is a fatal signal, you should still say so explicitly. Suppose something strange is going on, such as your -copy of the utility is out of synch, or you have encountered a bug in +copy of the utility is out of sync, or you have encountered a bug in the C library on your system. (This has happened!) Your copy might crash and ours would not. If you told us to expect a crash, then when ours fails to crash, we would know that the bug was not happening for diff --git a/gas/ChangeLog b/gas/ChangeLog index b12b230270b..cdf9095e814 100644 --- a/gas/ChangeLog +++ b/gas/ChangeLog @@ -1,3 +1,12 @@ +2006-07-24 Ralk Wildenhues + + * doc/all.texi, doc/as.texinfo, doc/c-arc.texi, doc/c-arm.texi, + doc/c-avr.texi, doc/c-bfin.texi, doc/c-i386.texi, + doc/c-i960.texi, doc/c-m32r.texi, doc/c-m68k.texi, + doc/c-mmix.texi, doc/c-pdp11.texi, doc/c-ppc.texi, + doc/c-tic54x.texi, doc/c-v850.texi, doc/c-xtensa.texi, + doc/c-z80.texi, doc/internals.texi: Fix some typos. + 2006-07-21 Nick Clifton * config/tc-sh.c (md_longopts): Add -EL and -EB for use by the diff --git a/gas/doc/all.texi b/gas/doc/all.texi index 3334cbc2f27..ddabb689703 100644 --- a/gas/doc/all.texi +++ b/gas/doc/all.texi @@ -64,7 +64,7 @@ @set Z80 @set Z8000 -@c Does this version of the assembler use the difference-table kluge? +@c Does this version of the assembler use the difference-table kludge? @set DIFF-TBL-KLUGE @c Do all machines described use IEEE floating point? diff --git a/gas/doc/as.texinfo b/gas/doc/as.texinfo index a86119e8cde..494381fdfc5 100644 --- a/gas/doc/as.texinfo +++ b/gas/doc/as.texinfo @@ -130,7 +130,7 @@ notice identical to this one except for the removal of this paragraph @subtitle Version @value{VERSION} @sp 1 @sp 13 -The Free Software Foundation Inc. thanks The Nice Computer +The Free Software Foundation Inc.@: thanks The Nice Computer Company of Australia for loaning Dean Elsner to write the first (Vax) version of @command{as} for Project @sc{gnu}. The proprietors, management and staff of TNCCA thank FSF for @@ -1181,13 +1181,13 @@ Assemble all undocumented Z80 instructions without warning. Issue a warning for undocumented Z80 instructions that also work on R800. @item -warn-unportable-instructions @itemx -Wup -Issue a warning for undocumented Z80 instructions that do notwork on R800. +Issue a warning for undocumented Z80 instructions that do not work on R800. @item -forbid-undocumented-instructions @itemx -Fud Treat all undocumented instructions as errors. @item -forbid-unportable-instructions @itemx -Fup -Treat undocumented Z80 intructions that do notwork on R800 as errors. +Treat undocumented Z80 instructions that do not work on R800 as errors. @end table @end ifset @@ -2678,7 +2678,7 @@ independently of any floating point hardware in the computer running @cindex bit fields @cindex constants, bit field You can also define numeric constants as @dfn{bit fields}. -specify two numbers separated by a colon--- +Specify two numbers separated by a colon--- @example @var{mask}:@var{value} @end example @@ -3276,7 +3276,7 @@ of the same name. The character has ASCII value of @samp{\002} (control-B). This is a serial number to keep the labels distinct. The first definition of @samp{0:} gets the number @samp{1}. The 15th definition of @samp{0:} gets the number @samp{15}, and so on. Likewise the first definition of @samp{1:} gets -the number @samp{1} and its 15th defintion gets @samp{15} as well. +the number @samp{1} and its 15th definition gets @samp{15} as well. @end table So for example, the first @code{1:} is named @code{L1@kbd{C-B}1}, the 44th @@ -3298,7 +3298,7 @@ dollar sign. eg @samp{@b{55$}}. They can also be distinguished from ordinary local labels by their transformed name which uses ASCII character @samp{\001} (control-A) as the magic character -to distinguish them from ordinary labels. Thus the 5th defintion of @samp{6$} +to distinguish them from ordinary labels. Thus the 5th definition of @samp{6$} is named @samp{L6@kbd{C-A}5}. @node Dot @@ -4078,7 +4078,7 @@ Don't forget to close the function by @cindex @code{cfi_endproc} directive @code{.cfi_endproc} is used at the end of a function where it closes its unwind entry previously opened by -@code{.cfi_startproc}. and emits it to @code{.eh_frame}. +@code{.cfi_startproc}, and emits it to @code{.eh_frame}. @section @code{.cfi_def_cfa @var{register}, @var{offset}} @code{.cfi_def_cfa} defines a rule for computing CFA as: @i{take @@ -4129,9 +4129,9 @@ to the @code{.debug_line} file name table. The @var{fileno} operand should be a unique positive integer to use as the index of the entry in the table. The @var{filename} operand is a C string literal. -The detail of filename indicies is exposed to the user because the filename +The detail of filename indices is exposed to the user because the filename table is shared with the @code{.debug_info} section of the dwarf2 debugging -information, and thus the user must know the exact indicies that table +information, and thus the user must know the exact indices that table entries will have. @section @code{.loc @var{fileno} @var{lineno} [@var{column}] [@var{options}]} @@ -5079,7 +5079,7 @@ You can write strings delimited in these other ways besides @table @code @item '@var{string}' -You can delimit strings with single-quote charaters. +You can delimit strings with single-quote characters. @item <@var{string}> You can delimit strings with matching angle brackets. @@ -6051,7 +6051,7 @@ This directive finds or creates a symbol @code{table} and creates a This directive finds the symbol @code{child} and finds or creates the symbol @code{parent} and then creates a @code{VTABLE_INHERIT} relocation for the parent whose addend is the value of the child symbol. As a special case the -parent name of @code{0} is treated as refering the @code{*ABS*} section. +parent name of @code{0} is treated as referring the @code{*ABS*} section. @end ifset @node Warning @@ -6607,7 +6607,7 @@ make a mistake. Even if the problem you experience is a fatal signal, you should still say so explicitly. Suppose something strange is going on, such as, your copy of -@command{@value{AS}} is out of synch, or you have encountered a bug in the C +@command{@value{AS}} is out of sync, or you have encountered a bug in the C library on your system. (This has happened!) Your copy might crash and ours would not. If you told us to expect a crash, then when ours fails to crash, we would know that the bug was not happening for us. If you had not told us to @@ -6760,7 +6760,7 @@ Timothy Wall, Michael Hayes, and Greg Smart contributed to the various tic* flavors. David Heine, Sterling Augustine, Bob Wilson and John Ruttenberg from Tensilica, -Inc. added support for Xtensa processors. +Inc.@: added support for Xtensa processors. Several engineers at Cygnus Support have also provided many small bug fixes and configuration enhancements. diff --git a/gas/doc/c-arc.texi b/gas/doc/c-arc.texi index 04544d1e495..7f8ed6eb400 100644 --- a/gas/doc/c-arc.texi +++ b/gas/doc/c-arc.texi @@ -230,7 +230,7 @@ Determines the kinds of suffixes to be allowed. Valid values are @code{SUFFIX_FLAG} which indicates the absence or presence of conditional suffixes and flag setting by the extension instruction. It is also possible to specify that an instruction sets the flags and -is conditional by using @code{SUFFIX_CODE} | @code{SUFFIX_FLAG}. +is condtional by using @code{SUFFIX_CODE} | @code{SUFFIX_FLAG}. @item @var{syntaxclass} Determines the syntax class for the instruction. It can have the @@ -251,7 +251,7 @@ Syntax Class Modifiers are: @item @code{OP1_MUST_BE_IMM}: Modifies syntax class SYNTAX_3OP, specifying that the first operand -of a three-operand instruction must be an immediate (i.e. the result +of a three-operand instruction must be an immediate (i.e., the result is discarded). OP1_MUST_BE_IMM is used by bitwise ORing it with SYNTAX_3OP as given in the example below. This could usually be used to set the flags using specific instructions and not retain results. diff --git a/gas/doc/c-arm.texi b/gas/doc/c-arm.texi index b5b9374b6bb..d9b7b26125a 100644 --- a/gas/doc/c-arm.texi +++ b/gas/doc/c-arm.texi @@ -254,7 +254,7 @@ and @item -meabi=@var{ver} This option specifies which EABI version the produced object files should conform to. -The following values are recognised: +The following values are recognized: @code{gnu}, @code{4} and @@ -358,7 +358,7 @@ For compatibility with older toolchains the assembler also accepts @cindex MOVW and MOVT relocations, ARM Relocations for @samp{MOVW} and @samp{MOVT} instructions can be generated by prefixing the value with @samp{#:lower16:} and @samp{#:upper16} -respectively. For example to load the 32-bit addresss of foo into r0: +respectively. For example to load the 32-bit address of foo into r0: @smallexample MOVW r0, #:lower16:foo diff --git a/gas/doc/c-avr.texi b/gas/doc/c-avr.texi index 515d2c689c3..9371bf2a364 100644 --- a/gas/doc/c-avr.texi +++ b/gas/doc/c-avr.texi @@ -109,7 +109,7 @@ statements. @cindex AVR register names @cindex register names, AVR -The AVR has 32 x 8-bit general purpouse working registers @samp{r0}, +The AVR has 32 x 8-bit general purpose working registers @samp{r0}, @samp{r1}, ... @samp{r31}. Six of the 32 registers can be used as three 16-bit indirect address register pointers for Data Space addressing. One of the these address diff --git a/gas/doc/c-bfin.texi b/gas/doc/c-bfin.texi index dcf649a2b89..0b8ae1d9f3e 100644 --- a/gas/doc/c-bfin.texi +++ b/gas/doc/c-bfin.texi @@ -97,9 +97,9 @@ The set of 32-bit registers (R0, R1, R2, R3, R4, R5, R6 and R7) that normally contain data for manipulation. These are abbreviated as D-register or Dreg. Data registers can be accessed as 32-bit registers or as two independent 16-bit registers. The least significant 16 bits -of each register is called the "low" half and is desginated with ".L" +of each register is called the "low" half and is designated with ".L" following the register name. The most significant 16 bits are called -the "high" half and is designated with ".H". following the name. +the "high" half and is designated with ".H" following the name. @smallexample R7.L, r2.h, r4.L, R0.H diff --git a/gas/doc/c-i386.texi b/gas/doc/c-i386.texi index 52f3110303f..665f42fa771 100644 --- a/gas/doc/c-i386.texi +++ b/gas/doc/c-i386.texi @@ -647,7 +647,7 @@ then stores the result in the 4 byte location @samp{mem}) @code{@value{AS}} supports Intel's MMX instruction set (SIMD instructions for integer data), available on Intel's Pentium MMX processors and Pentium II processors, AMD's K6 and K6-2 processors, -Cyrix' M2 processor, and probably others. It also supports AMD's 3DNow! +Cyrix' M2 processor, and probably others. It also supports AMD's 3DNow!@: instruction set (SIMD instructions for 32-bit floating point data) available on AMD's K6-2 processor and possibly others in the future. @@ -710,7 +710,7 @@ value @samp{4} onto the stack, decrementing @samp{%esp} by 2. @end smallexample The same code in a 16-bit code section would generate the machine -opcode bytes @samp{6a 04} (ie. without the operand size prefix), which +opcode bytes @samp{6a 04} (i.e., without the operand size prefix), which is correct since the processor default operand size is assumed to be 16 bits in a 16-bit code section. diff --git a/gas/doc/c-i960.texi b/gas/doc/c-i960.texi index 5dca1cf9c11..4d75bdfb8f7 100644 --- a/gas/doc/c-i960.texi +++ b/gas/doc/c-i960.texi @@ -69,7 +69,7 @@ Label: @var{BR} @end smallexample The counter following a branch records the number of times that branch -was @emph{not} taken; the differenc between the two counters is the +was @emph{not} taken; the difference between the two counters is the number of times the branch @emph{was} taken. @cindex @code{gbr960}, i960 postprocessor diff --git a/gas/doc/c-m32r.texi b/gas/doc/c-m32r.texi index 30cd355aede..218ed250a01 100644 --- a/gas/doc/c-m32r.texi +++ b/gas/doc/c-m32r.texi @@ -65,7 +65,7 @@ configured. @item -EL @cindex @code{-EL} option, M32R -This is a synonum for @emph{-little}. +This is a synonym for @emph{-little}. @item -big @cindex @code{-big} option, M32R @@ -110,7 +110,7 @@ implies @emph{-parallel}. Instructs @code{@value{AS}} to produce warning messages when questionable parallel instructions are encountered. This option is enabled by default, but @code{@value{GCC}} disables it when it invokes -@code{@value{AS}} directly. Questionable instructions are those whoes +@code{@value{AS}} directly. Questionable instructions are those whose behaviour would be different if they were executed sequentially. For example the code fragment @samp{mv r1, r2 || mv r3, r1} produces a different result from @samp{mv r1, r2 \n mv r3, r1} since the former @@ -135,7 +135,7 @@ option. @item -ignore-parallel-conflicts @cindex @samp{-ignore-parallel-conflicts} option, M32RX This option tells the assembler's to stop checking parallel -instructions for contraint violations. This ability is provided for +instructions for constraint violations. This ability is provided for hardware vendors testing chip designs and should not be used under normal circumstances. @@ -157,8 +157,8 @@ option. @item -warn-unmatched-high @cindex @samp{-warn-unmatched-high} option, M32R This option tells the assembler to produce a warning message if a -@code{.high} pseudo op is encountered without a mathcing @code{.low} -pseudo op. The presence of such an unmatches pseudo op usually +@code{.high} pseudo op is encountered without a matching @code{.low} +pseudo op. The presence of such an unmatched pseudo op usually indicates a programming error. @item -no-warn-unmatched-high @@ -280,14 +280,14 @@ instructions in the M32R2 ISA as well as the ordinary M32R ISA. The directive performs a similar thing as the @emph{-little} command line option. It tells the assembler to start producing little-endian code and data. This option should be used with care as producing -mixed-endian binary files is frought with danger. +mixed-endian binary files is fraught with danger. @cindex @code{.big} directive, M32RX @item .big The directive performs a similar thing as the @emph{-big} command line option. It tells the assembler to start producing big-endian code and data. This option should be used with care as producing -mixed-endian binary files is frought with danger. +mixed-endian binary files is fraught with danger. @end table @@ -328,7 +328,7 @@ instructions. @item unknown instruction @samp{...} This message is produced when the assembler encounters an instruction -which it does not recognise. +which it does not recognize. @item only the NOP instruction can be issued in parallel on the m32r This message is produced when the assembler encounters a parallel diff --git a/gas/doc/c-m68k.texi b/gas/doc/c-m68k.texi index d4da2a1ea45..0f8bb7853ef 100644 --- a/gas/doc/c-m68k.texi +++ b/gas/doc/c-m68k.texi @@ -284,7 +284,7 @@ The following addressing modes are understood: @item Address Register @samp{%a0} through @samp{%a7}@* -@samp{%a7} is also known as @samp{%sp}, i.e. the Stack Pointer. @code{%a6} +@samp{%a7} is also known as @samp{%sp}, i.e., the Stack Pointer. @code{%a6} is also known as @samp{%fp}, the Frame Pointer. @item Address Register Indirect @@ -346,7 +346,7 @@ The following additional addressing modes are understood: @table @dfn @item Address Register Indirect @samp{(%a0)} through @samp{(%a7)}@* -@samp{%a7} is also known as @samp{%sp}, i.e. the Stack Pointer. @code{%a6} +@samp{%a7} is also known as @samp{%sp}, i.e., the Stack Pointer. @code{%a6} is also known as @samp{%fp}, the Frame Pointer. @item Address Register Postincrement @@ -445,11 +445,11 @@ This directive is identical to a @code{.space} directive. @cindex @code{arch} directive, M680x0 @item .arch @var{name} -Select the target architecture and extension features. Valid valuse +Select the target architecture and extension features. Valid values for @var{name} are the same as for the @option{-march} command line option. This directive cannot be specified after any instructions have been assembled. If it is given multiple times, -or in conjuction with the @option{-march} option, all uses must be for +or in conjunction with the @option{-march} option, all uses must be for the same architecture and extension set. @cindex @code{cpu} directive, M680x0 @@ -458,7 +458,7 @@ Select the target cpu. Valid valuse for @var{name} are the same as for the @option{-mcpu} command line option. This directive cannot be specified after any instructions have been assembled. If it is given multiple times, -or in conjuction with the @option{-mopt} option, all uses must be for +or in conjunction with the @option{-mopt} option, all uses must be for the same cpu. @end table diff --git a/gas/doc/c-mmix.texi b/gas/doc/c-mmix.texi index 8e47fa4a979..257e3a69d8a 100644 --- a/gas/doc/c-mmix.texi +++ b/gas/doc/c-mmix.texi @@ -530,7 +530,7 @@ Operand syntax is a bit stricter with @code{@value{AS}} than must write @code{addu $1,$2,3}. You can't LOC to a lower address than those already visited -(i.e. ``backwards''). +(i.e., ``backwards''). A LOC directive must come before any emitted code. diff --git a/gas/doc/c-pdp11.texi b/gas/doc/c-pdp11.texi index d714b28343a..78f2cf41f63 100644 --- a/gas/doc/c-pdp11.texi +++ b/gas/doc/c-pdp11.texi @@ -311,7 +311,7 @@ an immediate constants, while in BSD syntax the character for this purpose is @code{$}. @cindex PDP-11 general-purpose register syntax -eneral-purpose registers are named @code{r0} through @code{r7}. +general-purpose registers are named @code{r0} through @code{r7}. Mnemonic alternatives for @code{r6} and @code{r7} are @code{sp} and @code{pc}, respectively. diff --git a/gas/doc/c-ppc.texi b/gas/doc/c-ppc.texi index 08b2271d125..b5e26fd0a8d 100644 --- a/gas/doc/c-ppc.texi +++ b/gas/doc/c-ppc.texi @@ -95,10 +95,10 @@ Allow symbolic names for registers. Do not allow symbolic names for registers. @item -mrelocatable -Support for GCC's -mrelocatble option. +Support for GCC's -mrelocatable option. @item -mrelocatable-lib -Support for GCC's -mrelocatble-lib option. +Support for GCC's -mrelocatable-lib option. @item -memb Set PPC_EMB bit in ELF flags. diff --git a/gas/doc/c-tic54x.texi b/gas/doc/c-tic54x.texi index 374def39e63..85b2fdad151 100644 --- a/gas/doc/c-tic54x.texi +++ b/gas/doc/c-tic54x.texi @@ -32,7 +32,7 @@ @cindex options, TIC54X @cindex TIC54X options -The TMS320C54x version of @code{@value{AS}} has a few machine-dependent options. +The TMS320C54X version of @code{@value{AS}} has a few machine-dependent options. @cindex @samp{-mfar-mode} option, far-mode @cindex @samp{-mf} option, far-mode @@ -450,7 +450,7 @@ points to the word that contains the specified field. @itemx .def @var{symbol} [,...,@var{symbol_n}] @itemx .ref @var{symbol} [,...,@var{symbol_n}] @code{.def} nominally identifies a symbol defined in the current file -and availalbe to other files. @code{.ref} identifies a symbol used in +and available to other files. @code{.ref} identifies a symbol used in the current file but defined elsewhere. Both map to the standard @code{.global} directive. @@ -685,7 +685,7 @@ values are accepted, the op is ignored. @cindex TIC54X-specific macros @cindex macros, TIC54X -Macros do not require explicit dereferencing of arguments (i.e. \ARG). +Macros do not require explicit dereferencing of arguments (i.e., \ARG). During macro expansion, the macro parameters are converted to subsyms. If the number of arguments passed the macro invocation exceeds the diff --git a/gas/doc/c-v850.texi b/gas/doc/c-v850.texi index 445be057ef3..d899d5df2a2 100644 --- a/gas/doc/c-v850.texi +++ b/gas/doc/c-v850.texi @@ -267,7 +267,7 @@ the immediate operand field of the given instruction. For example: computes the difference between the address of labels 'here' and 'there', takes the upper 16 bits of this difference, shifts it down 16 -bits and then mutliplies it by the lower 16 bits in register 5, putting +bits and then multiplies it by the lower 16 bits in register 5, putting the result into register 6. @cindex @code{lo} pseudo-op, V850 diff --git a/gas/doc/c-xtensa.texi b/gas/doc/c-xtensa.texi index 33035ad8b48..2a1fb54b0b0 100644 --- a/gas/doc/c-xtensa.texi +++ b/gas/doc/c-xtensa.texi @@ -428,7 +428,7 @@ The @code{L8UI} machine instruction can only be used with immediate offsets in the range from 0 to 255. The @code{L16SI} and @code{L16UI} machine instructions can only be used with offsets from 0 to 510. The @code{L32I} machine instruction can only be used with offsets from 0 to -1020. A load offset outside these ranges can be materalized with +1020. A load offset outside these ranges can be materialized with an @code{L32R} instruction if the destination register of the load is different than the source address register. For example: @@ -489,7 +489,7 @@ is assembled into the following: @cindex Xtensa directives @cindex directives, Xtensa -The Xtensa assember supports a region-based directive syntax: +The Xtensa assembler supports a region-based directive syntax: @smallexample .begin @var{directive} [@var{options}] diff --git a/gas/doc/c-z80.texi b/gas/doc/c-z80.texi index 76e8410840a..c52268a8cfb 100644 --- a/gas/doc/c-z80.texi +++ b/gas/doc/c-z80.texi @@ -59,7 +59,7 @@ Treat undocumented z80-instructions that do not work on R800 as errors. @item -r800 Produce code for the R800 processor. The assembler does not support undocumented instructions for the R800. -In line with common practice, @code{@value{AS}} uses Z80 instriction names +In line with common practice, @code{@value{AS}} uses Z80 instruction names for the R800 processor, as far as they exist. @end table @@ -105,7 +105,7 @@ A backslash @samp{\} is an ordinary character for the Z80 assembler. @cindex single quote, Z80 @cindex Z80 ' The single quote @samp{'} must be followed by a closing quote. If there -is one character inbetween, it is a character constant, otherwise it is +is one character in between, it is a character constant, otherwise it is a string constant. @node Z80-Regs @@ -114,7 +114,7 @@ a string constant. @cindex register names, Z80 The registers are referred to with the letters assigned to them by -Zilog. In addition @command{@value{AS}} recognises @samp{ixl} and +Zilog. In addition @command{@value{AS}} recognizes @samp{ixl} and @samp{ixh} as the least and most significant octet in @samp{ix}, and similarly @samp{iyl} and @samp{iyh} as parts of @samp{iy}. @@ -171,7 +171,7 @@ overflow. @item ds @var{count}[, @var{value}] @itemx defs @var{count}[, @var{value}] @c Synonyms for @code{ds.b}, -@c which should have been described elsewhre +@c which should have been described elsewhere Fill @var{count} bytes in the object file with @var{value}, if @var{value} is omitted it defaults to zero. @@ -188,7 +188,7 @@ This is a normal instruction on Z80, and not an assembler directive. A synonym for @xref{Section}, no second argument should be given. @ignore -The following attributes will possibly be recognised in the future +The following attributes will possibly be recognized in the future @table @code @item abs The section is to be absolute. @code{@value{AS}} will issue an error @@ -212,7 +212,7 @@ The section is marked as read only. @node Z80 Opcodes @section Opcodes -In line with commmon practice Z80 mnonics are used for both the Z80 and +In line with common practice, Z80 mnemonics are used for both the Z80 and the R800. In many instructions it is possible to use one of the half index diff --git a/gas/doc/internals.texi b/gas/doc/internals.texi index dffdb1e04fa..16a64637e31 100644 --- a/gas/doc/internals.texi +++ b/gas/doc/internals.texi @@ -838,7 +838,7 @@ GAS will call @code{md_parse_option} whenever @code{getopt} returns an unrecognized code, presumably indicating a special code value which appears in @code{md_longopts}. This function should return non-zero if it handled the option and zero otherwise. There is no need to print a message about an option -not being recognised. This will be handled by the generic code. +not being recognized. This will be handled by the generic code. GAS will call @code{md_show_usage} when a usage message is printed; it should print a description of the machine specific options. @code{md_after_pase_args}, @@ -891,7 +891,7 @@ If this macro is defined, GAS will use it instead of @code{comment_chars}. @cindex tc_symbol_chars If this macro is defined, it is a pointer to a null terminated list of characters which may appear in an operand. GAS already assumes that all -alphanumberic characters, and @samp{$}, @samp{.}, and @samp{_} may appear in an +alphanumeric characters, and @samp{$}, @samp{.}, and @samp{_} may appear in an operand (see @samp{symbol_chars} in @file{app.c}). This macro may be defined to treat additional characters as appearing in an operand. This affects the way in which GAS removes whitespace before passing the string to @@ -1609,7 +1609,7 @@ symbol's flags. @item obj_clear_weak_hook @cindex obj_clear_weak_hook -If you define this macro, @code{S_CLEAR_WEAKREFD} will call it after clearning +If you define this macro, @code{S_CLEAR_WEAKREFD} will call it after cleaning the @code{weakrefd} flag, but before modifying any other flags. @item obj_frob_file diff --git a/gprof/ChangeLog b/gprof/ChangeLog index c98e984928a..3161cbea49d 100644 --- a/gprof/ChangeLog +++ b/gprof/ChangeLog @@ -1,3 +1,7 @@ +2006-07-24 Ralk Wildenhues + + * gprof.texi: Fix some typos. + 2006-06-07 Joseph S. Myers * po/Make-in (pdf, ps): New dummy targets. diff --git a/gprof/gprof.texi b/gprof/gprof.texi index a81b109ec52..3c141d9aa29 100644 --- a/gprof/gprof.texi +++ b/gprof/gprof.texi @@ -442,7 +442,7 @@ The order of these options does not matter. @menu * Output Options:: Controlling @code{gprof}'s output style -* Analysis Options:: Controlling how @code{gprof} analyses its data +* Analysis Options:: Controlling how @code{gprof} analyzes its data * Miscellaneous Options:: * Deprecated Options:: Options you no longer need to use, but which have been retained for compatibility @@ -559,7 +559,7 @@ Normally, @code{gprof} prints annotated source files to standard-output. If this option is specified, annotated source for a file named @file{path/@var{filename}} is generated in the file @file{@var{filename}-ann}. If the underlying -filesystem would truncate @file{@var{filename}-ann} so that it +file system would truncate @file{@var{filename}-ann} so that it overwrites the original @file{@var{filename}}, @code{gprof} generates annotated source in the file @file{@var{filename}.ann} instead (if the original file name has an extension, that extension is @emph{replaced} @@ -654,7 +654,7 @@ The @samp{-a} option causes @code{gprof} to suppress the printing of statically declared (private) functions. (These are functions whose names are not listed as global, and which are not visible outside the file/function/block where they were defined.) Time spent in these -functions, calls to/from them, etc, will all be attributed to the +functions, calls to/from them, etc., will all be attributed to the function that was loaded directly before it in the executable file. @c This is compatible with Unix @code{gprof}, but a bad idea. This option affects both the flat profile and the call graph. @@ -1685,7 +1685,7 @@ Because @code{gprof} can only report call times and counts by function, the best way to get finer-grained information on where the program is spending its time is to re-factor large functions into sequences of calls to smaller ones. Beware however that this can introduce -artifical hot spots since compiling with @samp{-pg} adds a significant +artificial hot spots since compiling with @samp{-pg} adds a significant overhead to function calls. An alternative solution is to use a non-intrusive profiler, e.g.@: oprofile. @@ -1722,7 +1722,7 @@ gprof fastprog gmon.sum @end example If your program is completely deterministic, all the call counts -will be simple multiples of 100 (i.e. a function called once in +will be simple multiples of 100 (i.e., a function called once in each run will appear with a call count of 100). @end table diff --git a/ld/ChangeLog b/ld/ChangeLog index 407d4afffdc..c78c52974dd 100644 --- a/ld/ChangeLog +++ b/ld/ChangeLog @@ -1,3 +1,8 @@ +2006-07-24 Ralk Wildenhues + + * ld.texinfo: Fix spelling mistakes. + * ldint.texinfo: Likewise. + 2006-07-23 Sonal Santan * ldlang.c (lang_section_bst): New structure for sorting sections diff --git a/ld/ld.texinfo b/ld/ld.texinfo index 687f19c78c7..f3d95805188 100644 --- a/ld/ld.texinfo +++ b/ld/ld.texinfo @@ -1461,7 +1461,7 @@ SunOS, the linker will form a runtime search patch out of all the runtime search path will be formed exclusively using the @option{-rpath} options, ignoring the @option{-L} options. This can be useful when using gcc, which adds many @option{-L} options which may be on NFS mounted -filesystems. +file systems. For compatibility with other ELF linkers, if the @option{-R} option is followed by a directory name, rather than a file name, it is treated as @@ -2037,9 +2037,9 @@ symbols before they are exported. @kindex --large-address-aware @item --large-address-aware -If given, the appropriate bit in the ``Charateristics'' field of the COFF +If given, the appropriate bit in the ``Characteristics'' field of the COFF header is set to indicate that this executable supports virtual addresses -greater than 2 gigabytes. This should be used in conjuction with the /3GB +greater than 2 gigabytes. This should be used in conjunction with the /3GB or /USERVA=@var{value} megabytes switch in the ``[operating systems]'' section of the BOOT.INI. Otherwise, this bit has no effect. [This option is specific to PE targeted ports of the linker] @@ -2681,7 +2681,7 @@ setting afterwards. @item OUTPUT(@var{filename}) @kindex OUTPUT(@var{filename}) -@cindex output file name in linker scripot +@cindex output file name in linker script The @code{OUTPUT} command names the output file. Using @code{OUTPUT(@var{filename})} in the linker script is exactly like using @samp{-o @var{filename}} on the command line (@pxref{Options,,Command @@ -5200,7 +5200,7 @@ page of memory, and changes them to use the 8 bit address form. the top page of memory). @item system control instructions -@command{ld} finds all @code{ldc.w, stc.w} instrcutions which use the +@command{ld} finds all @code{ldc.w, stc.w} instructions which use the 32 bit absolute address form, but refer to the top page of memory, and changes them to use 16 bit address form. (That is: the linker turns @samp{ldc.w @code{@@}@var{aa}:32,ccr} into @@ -5345,7 +5345,7 @@ point to the function trampoline. @cindex ARM interworking support @kindex --support-old-code For the ARM, @command{ld} will generate code stubs to allow functions calls -betweem ARM and Thumb code. These stubs only work with code that has +between ARM and Thumb code. These stubs only work with code that has been compiled and assembled with the @samp{-mthumb-interwork} command line option. If it is necessary to link with old ARM object files or libraries, which have not been compiled with the -mthumb-interwork @@ -5745,7 +5745,7 @@ header format depends on the default specified by the specific target. @section @command{ld} and WIN32 (cygwin/mingw) This section describes some of the win32 specific @command{ld} issues. -See @ref{Options,,Command Line Options} for detailed decription of the +See @ref{Options,,Command Line Options} for detailed description of the command line options mentioned here. @table @emph @@ -5822,8 +5822,8 @@ The optional @code{LIBRARY } command indicates the @emph{internal} name of the output DLL. If @samp{} does not include a suffix, the default library suffix, @samp{.DLL} is appended. -When the .DEF file is used to build an application. rather than a -library, the @code{NAME } command shoud be used instead of +When the .DEF file is used to build an application, rather than a +library, the @code{NAME } command should be used instead of @code{LIBRARY}. If @samp{} does not include a suffix, the default executable suffix, @samp{.EXE} is appended. @@ -5917,7 +5917,7 @@ code the header must declare them as dllimport. There are a number of idioms that are typically used to do this; often client code can omit the __declspec() declaration completely. See @samp{--enable-auto-import} and @samp{automatic data imports} for more -imformation. +information. @end table @cindex automatic data imports @@ -5929,7 +5929,7 @@ issue. This increases the effort necessary to port existing Un*x code to these platforms, especially for large c++ libraries and applications. The auto-import feature, which was initially provided by Paul Sokolovsky, allows one to omit the -decorations to archieve a behavior that conforms to that on POSIX/Un*x +decorations to achieve a behavior that conforms to that on POSIX/Un*x platforms. This feature is enabled with the @samp{--enable-auto-import} command-line option, although it is enabled by default on cygwin/mingw. The @samp{--enable-auto-import} option itself now serves mainly to @@ -5973,7 +5973,7 @@ enabled as needed. The cygwin/mingw ports of @command{ld} support the direct linking, including data symbols, to a dll without the usage of any import libraries. This is much faster and uses much less memory than does the -traditional import library method, expecially when linking large +traditional import library method, especially when linking large libraries or applications. When @command{ld} creates an import lib, each function or variable exported from the dll is stored in its own bfd, even though a single bfd could contain many exports. The overhead involved in @@ -6454,7 +6454,7 @@ a chance to make a mistake. Even if the problem you experience is a fatal signal, you should still say so explicitly. Suppose something strange is going on, such as, your -copy of @command{ld} is out of synch, or you have encountered a bug in the +copy of @command{ld} is out of sync, or you have encountered a bug in the C library on your system. (This has happened!) Your copy might crash and ours would not. If you told us to expect a crash, then when ours fails to crash, we would know that the bug was not happening for us. If diff --git a/ld/ldint.texinfo b/ld/ldint.texinfo index dc6e9a65ef3..597deb2e782 100644 --- a/ld/ldint.texinfo +++ b/ld/ldint.texinfo @@ -179,10 +179,10 @@ as well as some conventional shell variables interpreted by the @item SCRIPT_NAME This is the name of the @file{scripttempl} script to use. If @code{SCRIPT_NAME} is set to @var{script}, @file{genscripts.sh} will use -the script @file{scriptteml/@var{script}.sc}. +the script @file{scripttempl/@var{script}.sc}. @item TEMPLATE_NAME -This is the name of the @file{emultemlp} script to use. If +This is the name of the @file{emultempl} script to use. If @code{TEMPLATE_NAME} is set to @var{template}, @file{genscripts.sh} will use the script @file{emultempl/@var{template}.em}. If this variable is not set, the default value is @samp{generic}. @@ -290,7 +290,7 @@ option. The output has an extension of The @file{scripttempl} script is only invoked with @code{LD_FLAG} set to this value if @code{GENERATE_COMBRELOC_SCRIPT} is defined in the @file{emulparams} file or if @code{SCRIPT_NAME} is @code{elf} and -@code{GENERATE_SHLIB_SCRIPT} is defined in the @file{emulparms} file. +@code{GENERATE_SHLIB_SCRIPT} is defined in the @file{emulparams} file. The @file{emultempl} script must arrange to use this script at the appropriate time, normally when the linker is invoked with the @code{-shared -z combreloc} option. The output has an extension of @file{.xsc}. @@ -644,7 +644,7 @@ Motivation The obvious and only way to get rid of dllimport insanity is to make client access variable directly in the DLL, bypassing the extra dereference imposed by ordinary DLL runtime linking. -I.e., whenever client contains someting like +I.e., whenever client contains something like @code{mov dll_var,%eax,} @@ -653,7 +653,7 @@ into loaded DLL. The aim is to make OS loader do so, and than make ld help with that. Import section of PE made following way: there's a vector of structures each describing imports from particular DLL. Each such structure points to two other -parellel vectors: one holding imported names, and one which +parallel vectors: one holding imported names, and one which will hold address of corresponding imported name. So, the solution is de-vectorize these structures, making import locations be sparse and pointing directly into code. -- 2.30.2