From: Andrew Cagney <cagney@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/mips] 128-bit long doubles for N32/N64
Date: Mon, 26 Jul 2004 22:19:00 -0000 [thread overview]
Message-ID: <41058380.6050407@gnu.org> (raw)
In-Reply-To: <20040722154456.GG1289@gnat.com>
Does long_double's floatformat need to be set?
> Index: mips-tdep.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/mips-tdep.c,v
> retrieving revision 1.301
> diff -u -p -r1.301 mips-tdep.c
> --- mips-tdep.c 10 Jul 2004 01:17:52 -0000 1.301
> +++ mips-tdep.c 22 Jul 2004 15:37:12 -0000
> @@ -5689,6 +5689,7 @@ 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);
> break;
> case MIPS_ABI_N64:
> set_gdbarch_push_dummy_call (gdbarch, mips_n32n64_push_dummy_call);
> @@ -5699,6 +5700,7 @@ 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);
> break;
> default:
> internal_error (__FILE__, __LINE__, "unknown ABI in switch");
Andrew
next prev parent reply other threads:[~2004-07-26 22:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 15:44 Joel Brobecker
2004-07-26 22:19 ` Andrew Cagney [this message]
2004-07-26 22:45 ` Joel Brobecker
2004-07-27 15:37 ` Andrew Cagney
2004-08-02 1:15 ` Joel Brobecker
2004-08-02 1:43 ` Michael Chastain
2004-08-02 18:31 ` Andrew Cagney
2004-08-03 1:13 ` Joel Brobecker
2004-08-03 1:59 ` Andrew Cagney
2004-08-03 4:39 ` Joel Brobecker
2004-08-03 7:27 ` Mark Kettenis
2004-08-03 13:31 ` Paul Koning
2004-08-04 4:00 ` Alexandre Oliva
2004-08-04 7:19 ` Mark Kettenis
2004-08-03 3:19 ` Michael Chastain
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=41058380.6050407@gnu.org \
--to=cagney@gnu.org \
--cc=brobecker@gnat.com \
--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