summaryrefslogtreecommitdiff
path: root/bfd/aout-ns32k.c
diff options
context:
space:
mode:
authorAlan Modra <amodra@bigpond.net.au>2003-06-25 06:40:25 +0000
committerAlan Modra <amodra@bigpond.net.au>2003-06-25 06:40:25 +0000
commit13bc6701a7ec432cfab9aa76f954eb9619b59572 (patch)
treed18138163ceec020b0d615db75516a0fe239913e /bfd/aout-ns32k.c
parent1a0c77687a77a46d904b2823b24ba90aa40e36b6 (diff)
downloadgdb-13bc6701a7ec432cfab9aa76f954eb9619b59572.tar.gz
Correct spelling of "relocatable".
Diffstat (limited to 'bfd/aout-ns32k.c')
-rw-r--r--bfd/aout-ns32k.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/bfd/aout-ns32k.c b/bfd/aout-ns32k.c
index 0972b5db187..8092705ba11 100644
--- a/bfd/aout-ns32k.c
+++ b/bfd/aout-ns32k.c
@@ -65,7 +65,7 @@ MY(put_reloc) PARAMS ((bfd *, int, int, bfd_vma, reloc_howto_type *,
struct reloc_std_external *));
/* The ns32k series is ah, unusual, when it comes to relocation.
- There are three storage methods for relocateable objects. There
+ There are three storage methods for relocatable objects. There
are displacements, immediate operands and ordinary twos complement
data. Of these, only the last fits into the standard relocation
scheme. Immediate operands are stored huffman encoded and