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 00:49:00 -0000 [thread overview]
Message-ID: <20040722004808.GB27215@nevyn.them.org> (raw)
In-Reply-To: <20040722004640.GS1278@gnat.com>
On Wed, Jul 21, 2004 at 05:46:40PM -0700, Joel Brobecker wrote:
> > I'm suggesting that this change belongs in mips-tdep.c rather than in
> > an OSABI handler. Unfortunately I'm not set up to test on mips64-linux
> > at the moment (and results were pretty dismal, though not quite as bad
> > as Irix).
>
> But would this change be applicable to NBSD as well? I am happy to
> install this change mips-tdep if you think long doubles are 16 bytes
> long on all mips targets. The only problem is that I won't be able to
> test it on anything but IRIX.
I don't think NetBSD even supports mips64. Not in GCC HEAD, at least.
According to GCC long double is 128-bit for all n64 and n32 targets.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-07-22 0:49 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 [this message]
[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
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=20040722004808.GB27215@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