Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] Add BE/LE floating-point type & format tables
Date: Sun, 08 Aug 2004 19:51:00 -0000	[thread overview]
Message-ID: <200408081951.i78JpTxK005673@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <4116617A.8010601@gnu.org> (message from Andrew Cagney on Sun, 08 Aug 2004 13:23:06 -0400)

   Date: Sun, 08 Aug 2004 13:23:06 -0400
   From: Andrew Cagney <cagney@gnu.org>

   2004-08-08  Andrew Cagney  <cagney@gnu.org>

	   * gdbtypes.c (builtin_type_arm_ext, builtin_type_ieee_single)
	   (builtin_type_ieee_double, builtin_type_ia64_quad)
	   (builtin_type_ia64_spill, _initialize_gdbtypes): Add tables of
	   BE/LE floating-point types.
	   * gdbtypes.h (builtin_type_arm_ext, builtin_type_ieee_single)
	   (builtin_type_ieee_double, builtin_type_ia64_quad)
	   (builtin_type_ia64_spill): Declare.
	   * doublest.c (_initialize_doublest, floatformat_ieee_single)
	   (floatformat_ieee_double, floatformat_arm_ext)
	   (floatformat_ia64_spill, floatformat_ia64_quad): Add tables
	   of LE/BE floatformats.	
	   * doublest.h: (struct floatformat, floatformat_ieee_single)
	   (floatformat_ieee_double, floatformat_arm_ext)
	   (floatformat_ia64_spill, floatformat_ia64_quad): Declare.

   I'll follow up with a couple uses.

You'd better do that because right now I don't see where this is
heading.

Anyway, could we rename floatformat_ia64_quad to
floatformat_ieee_quad.  There are quite a few systems out there that
use or will be using the same format, and I believe i will be in a new
revision of the official IEEE standard for it.

Mark


  reply	other threads:[~2004-08-08 19:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-08 17:23 Andrew Cagney
2004-08-08 19:51 ` Mark Kettenis [this message]
2004-08-09 13:58   ` Andrew Cagney
2004-08-09 15:12     ` Mark Kettenis
2004-08-24 22:39       ` Andrew Cagney

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=200408081951.i78JpTxK005673@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --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