darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

* config/i386/tm-i386.h (TARGET_LONG_DOUBLE_FORMAT,

Browse source 
TARGET_LONG_DOUBLE_BIT): Remove.  * i386-tdep.c
(i386_gdbarch_init): Initialize long_double_format and long_double
bit.
This commit is contained in:
Mark Kettenis 2002-06-14 21:17:28 +00:00
parent 8201327c40
commit 896fb97df8
3 changed files with 16 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
gdb/ChangeLog
View file

@ -1,5 +1,10 @@
2002-06-14 Mark Kettenis <kettenis@gnu.org>
* config/i386/tm-i386.h (TARGET_LONG_DOUBLE_FORMAT,
TARGET_LONG_DOUBLE_BIT): Remove. * i386-tdep.c
(i386_gdbarch_init): Initialize long_double_format and long_double
bit.
* config/i386/i386sol2.mt (TDEPFILES): Add i386-sol2-tdep.o and
i386bsd-tdep.o. Remove solib.o, solib-svr4.o and solib-legacy.o.
Move these to ...

13
gdb/config/i386/tm-i386.h
View file

@ -32,19 +32,6 @@ struct frame_saved_regs;
struct value;
struct type;
/* The format used for `long double' on almost all i386 targets is the
i387 extended floating-point format. In fact, of all targets in the
GCC 2.95 tree, only OSF/1 does it different, and insists on having
a `long double' that's not `long' at all. */
#define TARGET_LONG_DOUBLE_FORMAT &floatformat_i387_ext
/* Although the i386 extended floating-point has only 80 significant
bits, a `long double' actually takes up 96, probably to enforce
alignment. */
#define TARGET_LONG_DOUBLE_BIT 96
/* Number of traps that happen between exec'ing the shell to run an
inferior, and when we finally get to the inferior code. This is 2
on most implementations. */

11
gdb/i386-tdep.c
View file

@ -1351,6 +1351,17 @@ i386_gdbarch_init (struct gdbarch_info info, struct gdbarch_list *arches)
tdep->sigtramp_end = 0;
tdep->sc_pc_offset = -1;
/* The format used for `long double' on almost all i386 targets is
the i387 extended floating-point format. In fact, of all targets
in the GCC 2.95 tree, only OSF/1 does it different, and insists
on having a `long double' that's not `long' at all. */
set_gdbarch_long_double_format (gdbarch, &floatformat_i387_ext);
/* Although the i386 extended floating-point has only 80 significant
bits, a `long double' actually takes up 96, probably to enforce
alignment. */
set_gdbarch_long_double_bit (gdbarch, 96);
set_gdbarch_get_longjmp_target (gdbarch, i386_get_longjmp_target);
set_gdbarch_use_generic_dummy_frames (gdbarch, 0);