Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ken Raeburn <raeburn@raeburn.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org, binutils@sourceware.org, gcc-patches@gcc.org
Subject: Re: [RFA] Add some VAX floating point formats to floatformat.[ch]
Date: Tue, 23 Aug 2005 21:58:00 -0000	[thread overview]
Message-ID: <348FDCE8-5D87-4C13-AB77-B4BD4E47F9C5@raeburn.org> (raw)
In-Reply-To: <200508212153.j7LLrJXJ006901@elgar.sibelius.xs4all.nl>

On Aug 21, 2005, at 17:53, Mark Kettenis wrote:
> This patch adds support for the two VAX floating-point formats used by
> GCC for 'float' and 'double'.  The real guts are in gdb/doublest.c
> (which I wil post later to the gdb list); this only adds the
> description.

It's been a long time since I checked, but doesn't gcc support both  
of the "double"-size FP formats the VAX architecture has, in addition  
to the "float" format?

+const struct floatformat floatformat_vax_single =
+{
+  floatformat_vax, 32, 0, 1, 8, 129, 0, 9, 23,
+  floatformat_intbit_no,
+  "floatformat_vax_single",
+  floatformat_always_valid
+};
+const struct floatformat floatformat_vax_double =
+{
+  floatformat_vax, 64, 0, 1, 8, 129, 0, 9, 55,
+  floatformat_intbit_no,
+  "floatformat_vax_single",
+  floatformat_always_valid
+};

Shouldn't this one be labelled "floatformat_vax_double"?  (And maybe  
"_d" or "_g"?)


  parent reply	other threads:[~2005-08-22 21:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-21 21:59 Mark Kettenis
2005-08-22 10:22 ` Nick Clifton
2005-08-22 11:53   ` Mark Kettenis
2005-08-22 16:07     ` Nick Clifton
2005-08-22 16:26       ` Jan-Benedict Glaw
2005-08-22 18:32         ` Paul Koning
2005-08-22 18:40   ` DJ Delorie
2005-08-23 21:58 ` Ken Raeburn [this message]
2005-08-31  8:48   ` Mark Kettenis
2005-08-31 17:30     ` Jan-Benedict Glaw
     [not found]       ` <200508312142.j7VLgn8f019978@elgar.sibelius.xs4all.nl>
2005-11-02 10:20         ` Jan-Benedict Glaw

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=348FDCE8-5D87-4C13-AB77-B4BD4E47F9C5@raeburn.org \
    --to=raeburn@raeburn.org \
    --cc=binutils@sourceware.org \
    --cc=gcc-patches@gcc.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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