aboutsummaryrefslogtreecommitdiff
path: root/gdb/config
diff options
context:
space:
mode:
authorMark Kettenis <kettenis@gnu.org>2000-03-26 22:10:59 +0000
committerMark Kettenis <kettenis@gnu.org>2000-03-26 22:10:59 +0000
commit6e2e8c243b4d299d74031c798497b64751ab93ca (patch)
treed046ff605e0dea4b50a597e0194c7af022e91d12 /gdb/config
parentac27f131b2fc0c5e0872c5855c599974b7416d07 (diff)
downloadfsf-binutils-gdb-6e2e8c243b4d299d74031c798497b64751ab93ca.zip
fsf-binutils-gdb-6e2e8c243b4d299d74031c798497b64751ab93ca.tar.gz
fsf-binutils-gdb-6e2e8c243b4d299d74031c798497b64751ab93ca.tar.bz2
2000-03-27 Mark Kettenis <kettenis@gnu.org>
* config/i386/tm-i386.h: Fix typo. It is TARGET_LONG_DOUBLE_BIT instead of TARGET_LONG_DOUBLE_BITS. * config/i386/tm-i386mk.h: Likewise.
Diffstat (limited to 'gdb/config')
-rw-r--r--gdb/config/i386/tm-i386.h2
-rw-r--r--gdb/config/i386/tm-i386mk.h4
2 files changed, 3 insertions, 3 deletions
diff --git a/gdb/config/i386/tm-i386.h b/gdb/config/i386/tm-i386.h
index f241884..bcb99fc 100644
--- a/gdb/config/i386/tm-i386.h
+++ b/gdb/config/i386/tm-i386.h
@@ -39,7 +39,7 @@ struct type;
bits, a `long double' actually takes up 96, probably to enforce
alignment. */
-#define TARGET_LONG_DOUBLE_BITS 96
+#define TARGET_LONG_DOUBLE_BIT 96
/* Used for example in valprint.c:print_floating() to enable checking
for NaN's */
diff --git a/gdb/config/i386/tm-i386mk.h b/gdb/config/i386/tm-i386mk.h
index de66a69..892dc30 100644
--- a/gdb/config/i386/tm-i386mk.h
+++ b/gdb/config/i386/tm-i386mk.h
@@ -29,10 +29,10 @@
to `double'. However, I'm not sure what is the consequence of:
#define TARGET_LONG_DOUBLE_FORMAT TARGET_DOUBLE_FORMAT
- #define TARGET_LONG_DOUBLE_BITS TARGET_DOUBLE_BITS
+ #define TARGET_LONG_DOUBLE_BIT TARGET_DOUBLE_BIT
So I'll go with the current status quo instead. It looks like this
target won't compile anyway. Perhaps it should be obsoleted? */
#undef TARGET_LONG_DOUBLE_FORMAT
-#undef TARGET_LONG_DOUBLE_BITS
+#undef TARGET_LONG_DOUBLE_BIT