Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: DJ Delorie <dj@redhat.com>
Cc: zack@codesourcery.com, binutils@sources.redhat.com,
	gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Add host's floatformat
Date: Mon, 26 Jul 2004 21:12:00 -0000	[thread overview]
Message-ID: <410573AA.4090805@gnu.org> (raw)
In-Reply-To: <200405032234.i43MYC1W022010@greed.delorie.com>

[picking up a really old thread]

>>Really, I don't see why this is better than a hardwired table
>>> mapping CPU to floating point format.
> 
> 
> Because most FPUs are IEEE, so except for the ones that aren't, it
> will auto-detect the FPU type.  Having a table means that CPUs default
> to "broken", rather than defaulting to "probably works".
> 
> It also means we don't have to keep tweaking the table as people
> change their minds about CPU naming schemes

This assume that the floatformat code works.

Below is a table generated by using floatformat to convert the double 
1.0 into the corresponding architecture format.  Notice the arm_ext_big 
/ arm_littlebyte_bigword and double_big / double_littlebyte_bigword pairs:

3f800000                         floatformat_ieee_single_big
0000803f                         floatformat_ieee_single_little
3ff0000000000000                 floatformat_ieee_double_big
000000000000f03f                 floatformat_ieee_double_little
3ff0000000000000                 floatformat_ieee_double_littlebyte_bigword
0000000000000080ff3f             floatformat_i387_ext
3fff8000000000000000             floatformat_m88110_ext
3fff00008000000000000000         floatformat_m68881_ext
0000000000000080ff3f0000         floatformat_i960_ext
00003fff8000000000000000         floatformat_arm_ext_big
00003fff8000000000000000         floatformat_arm_ext_littlebyte_bigword
3ff00000000000000000000000000000 floatformat_m88110_ext_harris
3fffe000000000000000000000000000 floatformat_ia64_spill_big
00000000000000000000000000e0ff3f floatformat_ia64_spill_little
3fff0000000000000000000000000000 floatformat_ia64_quad_big
0000000000000000000000000000ff3f floatformat_ia64_quad_little

I'm withdrawing my patch.  I'll instead fix this as MarkK suggested - 
local to GDB.

Andrew



  reply	other threads:[~2004-07-26 21:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-01 12:53 Andrew Cagney
2004-05-01 13:25 ` DJ Delorie
2004-05-01 14:28   ` Andrew Cagney
2004-05-01 14:06 ` Andreas Schwab
2004-05-01 14:34 ` Mark Kettenis
2004-05-01 15:00   ` Andrew Cagney
2004-05-01 17:20 ` Andrew Cagney
2004-05-02 10:04   ` Mark Kettenis
2004-05-02 20:49   ` DJ Delorie
2004-05-02 20:49   ` DJ Delorie
2004-05-03 19:11     ` Andrew Cagney
2004-05-03 22:11       ` DJ Delorie
2004-05-03 22:29         ` Zack Weinberg
2004-05-03 22:34           ` DJ Delorie
2004-07-26 21:12             ` Andrew Cagney [this message]
2004-05-03 22:37         ` Andrew Cagney
2004-05-03 22:44           ` DJ Delorie
2004-05-03 23:21             ` Andrew Cagney
2004-05-03 23:48               ` DJ Delorie
2004-05-03 23:58                 ` Zack Weinberg
2004-05-04 14:11                   ` Andrew Cagney
2004-05-05 16:32                 ` Andrew Cagney
2004-05-05 17:05                   ` DJ Delorie
2004-07-29 19:35 ` Andrew Cagney
2004-07-30  9:46   ` Andreas Schwab
2004-07-30 13:26     ` Andrew Cagney
2004-11-20 18:17       ` Andreas Schwab

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=410573AA.4090805@gnu.org \
    --to=cagney@gnu.org \
    --cc=binutils@sources.redhat.com \
    --cc=dj@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=zack@codesourcery.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