summaryrefslogtreecommitdiff
path: root/bfd/bfd.c
diff options
context:
space:
mode:
authorKazu Hirata <kazu@codesourcery.com>2000-11-21 02:24:32 +0000
committerKazu Hirata <kazu@codesourcery.com>2000-11-21 02:24:32 +0000
commit831d560da225dcb4414bebcab1d126255f2cfd20 (patch)
tree7a569bf1043dd93afaf6851f042efd8323f277ce /bfd/bfd.c
parentaa9be74d4b992aceab67beadde1da94014bad25c (diff)
downloadgdb-831d560da225dcb4414bebcab1d126255f2cfd20.tar.gz
2000-11-20 Kazu Hirata <kazu@hxi.com>
* bfd-in.h: Fix formatting. * bfd-in2.h: Likewise. * bfd.c: Likewise. * bout.c: Likewise.
Diffstat (limited to 'bfd/bfd.c')
-rw-r--r--bfd/bfd.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/bfd/bfd.c b/bfd/bfd.c
index e11aaf47f7a..3372708e978 100644
--- a/bfd/bfd.c
+++ b/bfd/bfd.c
@@ -833,7 +833,7 @@ DESCRIPTION
Instead, we want to ask questions like "is this NNN byte sized
object I'm about to try read from file offset YYY reasonable?"
As as example of where we might do this, some object formats
- use string tables for which the first <<sizeof(long)>> bytes of the
+ use string tables for which the first <<sizeof (long)>> bytes of the
table contain the size of the table itself, including the size bytes.
If an application tries to read what it thinks is one of these
string tables, without some way to validate the size, and for
@@ -980,7 +980,7 @@ bfd_scan_vma (string, end, base)
int digit;
/* Let the host do it if possible. */
- if (sizeof(bfd_vma) <= sizeof(unsigned long))
+ if (sizeof (bfd_vma) <= sizeof (unsigned long))
return (bfd_vma) strtoul (string, (char **) end, base);
/* A negative base makes no sense, and we only need to go as high as hex. */