From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] mips-irix SEGV: long doubles are 128 bits long on IRIX
Date: Thu, 22 Jul 2004 02:21:00 -0000 [thread overview]
Message-ID: <20040722022031.GA30249@nevyn.them.org> (raw)
In-Reply-To: <20040722020854.GT1278@gnat.com>
On Wed, Jul 21, 2004 at 07:08:54PM -0700, Joel Brobecker wrote:
> > According to GCC long double is 128-bit for all n64 and n32 targets.
>
> OK. So I am planning on setting the size to 128-bit for the following
> ABIs, is this the correct list:
> . O64 (??? Didn't see any mention of this in the IRIX man pages)
> . EABI32, EABI64
> . N32/N64
> I will add the same set_gdbarch_...() call in each section of the case
> statement on mips_abi.
>
> Would that be the correct patch?
Ehm; no, I don't think so. I only said N32 and N64, and according to
GCC that's all it is. The older ABIs don't have 128-bit long double.
I think the best thing would be to make this change in mips-tdep; some
additional changes for Irix and/or Linux may be necessary to get the
format right, though.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-07-22 2:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 21:25 Joel Brobecker
2004-07-21 21:30 ` Daniel Jacobowitz
2004-07-21 23:33 ` Joel Brobecker
2004-07-22 0:40 ` Daniel Jacobowitz
2004-07-22 0:46 ` Joel Brobecker
2004-07-22 0:49 ` Daniel Jacobowitz
[not found] ` <mailpost.1090457371.25819@news-sj1-1>
2004-07-22 1:19 ` cgd
2004-07-22 1:27 ` Daniel Jacobowitz
2004-07-22 2:09 ` Joel Brobecker
2004-07-22 2:21 ` Daniel Jacobowitz [this message]
2004-07-22 2:34 ` Joel Brobecker
2004-07-22 2:36 ` Daniel Jacobowitz
2004-07-23 17:00 David Anderson
2004-07-26 22:18 ` Andrew Cagney
[not found] ` <mailpost.1090880398.10041@news-sj1-1>
2004-07-26 22:41 ` cgd
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=20040722022031.GA30249@nevyn.them.org \
--to=drow@false.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