From: Joel Brobecker <brobecker@gnat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/mips] Fix crash trying to print long double float
Date: Mon, 09 Aug 2004 05:46:00 -0000 [thread overview]
Message-ID: <20040809054623.GL1192@gnat.com> (raw)
In-Reply-To: <41165B7A.4010601@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
> >Tested on mips-irix. OK to apply?
>
> Yes, with these tweaks, commit:
Thanks. Here is what I just checked in:
2004-08-08 Joel Brobecker <brobecker@gnat.com>
* mips-tdep.c: Include "floatformat.h".
(n32n64_floatformat_always_valid): New function.
(floatformat_n32n64_long_double_big): New constant.
(mips_gdbarch_init): Set size and format of long double
for N32 and N64 ABIs.
* Makefile.in (mips-tdep.o): Update dependencies.
--
Joel
[-- Attachment #2: ld.diff --]
[-- Type: text/plain, Size: 3471 bytes --]
Index: mips-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/mips-tdep.c,v
retrieving revision 1.309
diff -u -p -r1.309 mips-tdep.c
--- mips-tdep.c 3 Aug 2004 01:12:43 -0000 1.309
+++ mips-tdep.c 8 Aug 2004 17:26:15 -0000
@@ -54,6 +54,7 @@
#include "frame-base.h"
#include "trad-frame.h"
#include "infcall.h"
+#include "floatformat.h"
static const struct objfile_data *mips_pdr_data;
@@ -149,6 +150,32 @@ struct gdbarch_tdep
const char **mips_processor_reg_names;
};
+static int
+n32n64_floatformat_always_valid (const struct floatformat *fmt,
+ const char *from)
+{
+ return 1;
+}
+
+/* FIXME: brobecker/2004-08-08: Long Double values are 128 bit long.
+ They are implemented as a pair of 64bit doubles where the high
+ part holds the result of the operation rounded to double, and
+ the low double holds the difference between the exact result and
+ the rounded result. So "high" + "low" contains the result with
+ added precision. Unfortunately, the floatformat structure used
+ by GDB is not powerful enough to describe this format. As a temporary
+ measure, we define a 128bit floatformat that only uses the high part.
+ We lose a bit of precision but that's probably the best we can do
+ for now with the current infrastructure. */
+
+static const struct floatformat floatformat_n32n64_long_double_big =
+{
+ floatformat_big, 128, 0, 1, 11, 1023, 2047, 12, 52,
+ floatformat_intbit_no,
+ "floatformat_ieee_double_big",
+ n32n64_floatformat_always_valid
+};
+
const struct mips_regnum *
mips_regnum (struct gdbarch *gdbarch)
{
@@ -6323,6 +6350,9 @@ mips_gdbarch_init (struct gdbarch_info i
set_gdbarch_long_bit (gdbarch, 32);
set_gdbarch_ptr_bit (gdbarch, 32);
set_gdbarch_long_long_bit (gdbarch, 64);
+ set_gdbarch_long_double_bit (gdbarch, 128);
+ set_gdbarch_long_double_format (gdbarch,
+ &floatformat_n32n64_long_double_big);
break;
case MIPS_ABI_N64:
set_gdbarch_push_dummy_call (gdbarch, mips_n32n64_push_dummy_call);
@@ -6333,6 +6363,9 @@ mips_gdbarch_init (struct gdbarch_info i
set_gdbarch_long_bit (gdbarch, 64);
set_gdbarch_ptr_bit (gdbarch, 64);
set_gdbarch_long_long_bit (gdbarch, 64);
+ set_gdbarch_long_double_bit (gdbarch, 128);
+ set_gdbarch_long_double_format (gdbarch,
+ &floatformat_n32n64_long_double_big);
break;
default:
internal_error (__FILE__, __LINE__, "unknown ABI in switch");
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/Makefile.in,v
retrieving revision 1.606
diff -u -p -r1.606 Makefile.in
--- Makefile.in 6 Aug 2004 19:14:44 -0000 1.606
+++ Makefile.in 8 Aug 2004 17:26:16 -0000
@@ -2206,7 +2206,8 @@ mips-tdep.o: mips-tdep.c $(defs_h) $(gdb
$(target_h) $(arch_utils_h) $(regcache_h) $(osabi_h) $(mips_tdep_h) \
$(block_h) $(reggroups_h) $(opcode_mips_h) $(elf_mips_h) \
$(elf_bfd_h) $(symcat_h) $(sim_regno_h) $(dis_asm_h) \
- $(frame_unwind_h) $(frame_base_h) $(trad_frame_h) $(infcall_h)
+ $(frame_unwind_h) $(frame_base_h) $(trad_frame_h) $(infcall_h) \
+ $(floatformat_h)
mipsv4-nat.o: mipsv4-nat.c $(defs_h) $(inferior_h) $(gdbcore_h) $(target_h) \
$(regcache_h) $(gregset_h)
mn10300-tdep.o: mn10300-tdep.c $(defs_h) $(frame_h) $(inferior_h) \
prev parent reply other threads:[~2004-08-09 5:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 18:16 Joel Brobecker
2004-08-06 20:24 ` Andrew Cagney
2004-08-06 20:38 ` Joel Brobecker
2004-08-06 21:03 ` Andrew Cagney
2004-08-07 17:18 ` Andrew Cagney
2004-08-06 20:32 ` Joel Brobecker
2004-08-07 18:01 ` Andrew Cagney
2004-08-07 18:09 ` Joel Brobecker
2004-08-07 18:22 ` Andrew Cagney
2004-08-08 6:59 ` Joel Brobecker
2004-08-08 16:57 ` Andrew Cagney
2004-08-09 5:46 ` Joel Brobecker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040809054623.GL1192@gnat.com \
--to=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox