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.
This commit is contained in:
Mark Kettenis
2000-03-26 22:10:59 +00:00
parent ac27f131b2
commit 6e2e8c243b
3 changed files with 9 additions and 3 deletions

View File

@ -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.

View File

@ -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 */

View File

@ -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