Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Paul Koning <pkoning@equallogic.com>
Cc: kettenis@jive.nl, brobecker@gnat.com, cagney@gnu.org,
	gdb-patches@sources.redhat.com
Subject: Re: [RFA/mips] 128-bit long doubles for N32/N64
Date: Wed, 04 Aug 2004 04:00:00 -0000	[thread overview]
Message-ID: <or657zd042.fsf@livre.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <16655.37815.285599.668840@gargle.gargle.HOWL>

On Aug  3, 2004, Paul Koning <pkoning@equallogic.com> wrote:

> Then again, I'm not sure why MIPS N32 is defined to have 128 bit
> floats in the first place.  It seems rather silly considering that
> there isn't any such data type in the machine instruction set.

The idea is of implementing long double as a pair of doubles is to
gain additional precision.  You can use the regular double floating
point instructions for all computations, and they can be implemented
somewhat efficiently.

This is the way IRIX does it; mips64-linux just uses standard IEEE
128-bit long doubles, so it has to be emulated.  That's mostly because
neither GCC nor glibc supported emulation with the IRIX format at the
time the port was written.  glibc still doesn't, AFAIK; GCC got
support for it, but IIRC it's darwin-specific.  AIX and Darwin also
use pairs of doubles as long doubles, but IIRC they have slightly
different conventions because AIX and IRIX disagree on the precision
they claim to support.

Hope this helps,

-- 
Alexandre Oliva             http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}


  reply	other threads:[~2004-08-04  4:00 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
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 [this message]
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=or657zd042.fsf@livre.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=brobecker@gnat.com \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@jive.nl \
    --cc=pkoning@equallogic.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