From: DJ Delorie <dj@redhat.com>
To: mark.kettenis@xs4all.nl
Cc: gcc-patches@gnu.org, binutils@sources.redhat.com,
gdb-patches@sources.redhat.com
Subject: Re: [RFA] s/char/void/g in floatformat.[ch]
Date: Mon, 15 Aug 2005 15:21:00 -0000 [thread overview]
Message-ID: <200508151452.j7FEqHxA010510@greed.delorie.com> (raw)
In-Reply-To: <200508151415.j7FEFGiV026412@elgar.sibelius.xs4all.nl> (message from Mark Kettenis on Mon, 15 Aug 2005 16:15:16 +0200 (CEST))
> The fact that the floatformat_xxx functions use `char *' for byte
> buffers used to store floating-point numbers doesn't help with GCC
> 4's `unsigned char' vs. '(signed) char' "madness". GDB now uses
> `gdb_byte' instead of '(unsigned) char', but we obviously cannot use
> that in libiberty. Therefore I propose we take the easy way out and
> use `void *' for the byte buffers. That should remove the need for
> nasty casts in all code that uses the floatformat stuff.
>
> Mark
Ok.
> P.S. I still think this code should be removed from libiberty/ and
> moved back into gdb/. Or does newlib still use it?
opcodes uses it for m68k.
prev parent reply other threads:[~2005-08-15 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 14:52 Mark Kettenis
2005-08-15 15:21 ` DJ Delorie [this message]
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=200508151452.j7FEqHxA010510@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc-patches@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--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