Fix spelling mistakes and typos in the GAS sources.

[thirdparty/binutils-gdb.git] / gas / config / tc-mips.c

diff --git a/gas/config/tc-mips.c b/gas/config/tc-mips.c
index 1487e73b856d3617a4d2e9049002d464177d4165..02a4e2240a72347c485a5ac564e5309af44f22a9 100644 (file)
--- a/gas/config/tc-mips.c
+++ b/gas/config/tc-mips.c
@@ -5031,7 +5031,7 @@ match_int_operand (struct mips_arg_info *arg,
        return FALSE;
 
       if (offset_reloc[0] != BFD_RELOC_UNUSED)
-       /* Relocation operators were used.  Accept the arguent and
+       /* Relocation operators were used.  Accept the argument and
           leave the relocation value in offset_expr and offset_relocs
           for the caller to process.  */
        return TRUE;
@@ -8608,7 +8608,7 @@ macro_build (expressionS *ep, const char *name, const char *fmt, ...)
     {
       /* Search until we get a match for NAME.  It is assumed here that
         macros will never generate MDMX, MIPS-3D, or MT instructions.
-        We try to match an instruction that fulfils the branch delay
+        We try to match an instruction that fulfills the branch delay
         slot instruction length requirement (if any) of the previous
         instruction.  While doing this we record the first instruction
         seen that matches all the other conditions and use it anyway
@@ -9514,7 +9514,7 @@ move_register (int dest, int source)
    LOCAL is the sum of a symbol and a 16-bit or 32-bit displacement.
    The two alternatives are:
 
-   Global symbol               Local sybmol
+   Global symbol               Local symbol
    -------------               ------------
    lw DEST,%got(SYMBOL)                lw DEST,%got(SYMBOL + OFFSET)
    ...                         ...
@@ -17618,11 +17618,11 @@ mips_fix_adjustable (fixS *fixp)
      is then identified by the section offset rather than by the symbol.
 
      However, if we're generating REL LO16 relocations, the offset is split
-     between the LO16 and parterning high part relocation.  The linker will
+     between the LO16 and partnering high part relocation.  The linker will
      need to recalculate the complete offset in order to correctly identify
      the merge data.
 
-     The linker has traditionally not looked for the parterning high part
+     The linker has traditionally not looked for the partnering high part
      relocation, and has thus allowed orphaned R_MIPS_LO16 relocations to be
      placed anywhere.  Rather than break backwards compatibility by changing
      this, it seems better not to force the issue, and instead keep the