From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Add support for VAX floating-point types
Date: Tue, 30 Aug 2005 02:52:00 -0000 [thread overview]
Message-ID: <20050830023841.GC16189@nevyn.them.org> (raw)
In-Reply-To: <200508212209.j7LM9PAX029015@elgar.sibelius.xs4all.nl>
On Mon, Aug 22, 2005 at 12:09:25AM +0200, Mark Kettenis wrote:
> OK, I admit it, all this work on VAX is pointless ... but fun ;-).
> And it actually improves the code too ;-). This patch depends on the
> libiberty patch I just sent out. Any objections? If not I'll check
> this in next weekend if possible.
>
> Mark
>
> Index: ChangeLog
> from Mark Kettenis <kettenis@gnu.org>
>
> * doublest.c (floatformat_normalize_byteorder): Handle
> floatformat_vax.
> (convert_doublest_to_floatformat): Use
> floatformat_normalize_byteorder to swap bytes if necessary.
None from me! Looks fine. Don't recall what happened to the libiberty
bits though.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-08-30 2:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 7:58 Mark Kettenis
2005-08-30 2:52 ` Daniel Jacobowitz [this message]
2005-08-30 21:27 ` Mark Kettenis
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=20050830023841.GC16189@nevyn.them.org \
--to=drow@false.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