Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Tue, 27 Jul 2004 15:37:00 -0000	[thread overview]
Message-ID: <410676AE.4010001@gnu.org> (raw)
In-Reply-To: <20040726224546.GB20596@gnat.com>

>>Does long_double's floatformat need to be set?
> 
> 
> Apparently not. Or I should say that I don't see any evidence that
> it should.

Check the floating-point tests in structs.exp and call-sc.exp.  There's 
hopefully also some sort of floating-point.exp test that confirms the 
basics.

Looking at the code, it appears to default to:

const struct floatformat *
default_double_format (struct gdbarch *gdbarch)
{
   int byte_order = gdbarch_byte_order (gdbarch);
   switch (byte_order)
     {
     case BFD_ENDIAN_BIG:
       return &floatformat_ieee_double_big;
     case BFD_ENDIAN_LITTLE:
       return &floatformat_ieee_double_little;
     default:
       internal_error (__FILE__, __LINE__,
                       "default_double_format: bad byte order");
     }
}

outch!

Andrew



  reply	other threads:[~2004-07-27 15:37 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 [this message]
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=410676AE.4010001@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