aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
Diffstat (limited to 'gdb')
-rw-r--r--gdb/ChangeLog6
-rw-r--r--gdb/config/i386/tm-i386.h2
-rw-r--r--gdb/config/i386/tm-i386mk.h4
3 files changed, 9 insertions, 3 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index de355b8..ed318ad 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,9 @@
+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.
+
2000-03-26 Mark Kettenis <kettenis@gnu.org>
Provide `long double' support for most i386 targets.
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