From: Michael Chastain <mec.gnu@mindspring.com>
To: cagney@gnu.org, brobecker@gnat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/mips] 128-bit long doubles for N32/N64
Date: Mon, 02 Aug 2004 01:43:00 -0000 [thread overview]
Message-ID: <410D9C59.nail5MB2I3MDA@mindspring.com> (raw)
In-Reply-To: <20040802011520.GA32638@gnat.com>
Joel Brobecker <brobecker@gnat.com> wrote:
> Let me know what you think.
I would suggest: take the explanation of "long double" on mips irix and
file it into a PR. If you could write a ten-line program and include
the C source and the assembly output in the PR, then the whole schmeer
can be there in GNATS for the day when somebody says "I have some free
time, let's work on MIPS PR's".
Michael C
next prev parent reply other threads:[~2004-08-02 1:43 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
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 [this message]
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=410D9C59.nail5MB2I3MDA@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=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