From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: cagney@gnu.org
Cc: eliz@gnu.org, mark.kettenis@xs4all.nl, gdb-patches@sources.redhat.com
Subject: Re: [commit] Use bfd_byte in value.h
Date: Sun, 01 May 2005 20:41:00 -0000 [thread overview]
Message-ID: <200505012041.j41KfFAA011729@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <42753958.70109@gnu.org> (message from Andrew Cagney on Sun, 01 May 2005 16:17:28 -0400)
Date: Sun, 01 May 2005 16:17:28 -0400
From: Andrew Cagney <cagney@gnu.org>
Eli,
Last time this came up I recommeded separating out the idea of gdb_byte
and proposed more formally. How is this going?
In the mean time though (then and now) I'll use bfd_byte as that lets me
move this code forward addressing the more immediate problem of not even
compiling with -Werror on GCC 4. With that done, i'm pretty sure that
we'll find the follow-on task of s/bfd_byte/gdb_byte/ trivial.
But why do we need special type at all. ISO C has void * for
arbitrary (byte) buffers. That's the type that should have been used
for the memory_insert_breakpoint/memory_remove_breakpoint interface
changes you just committed. Any implementation of that interface
should do the appropriate cast if it needs to do pointer arithmetic,
or needs to interpret the bytes as signed or unsigned. If we agree on
that, this makes the follow-in task you mention non-trivial. Since
you are alreading spending an effort on this, why not spend a small
amount of extra effort and fix things properly now?
Mark
next prev parent reply other threads:[~2005-05-01 20:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 16:27 Andrew Cagney
2005-04-28 19:19 ` Mark Kettenis
2005-04-28 19:21 ` Daniel Jacobowitz
2005-04-28 22:12 ` Andrew Cagney
2005-04-29 7:15 ` Eli Zaretskii
2005-05-01 20:19 ` Andrew Cagney
2005-05-01 20:41 ` Mark Kettenis [this message]
2005-05-01 21:13 ` Eli Zaretskii
2005-05-01 23:04 ` Andrew Cagney
2005-05-02 19:12 ` Eli Zaretskii
2005-05-03 14:43 ` Andrew Cagney
2005-05-03 19:55 ` Eli Zaretskii
2005-05-03 20:01 ` Daniel Jacobowitz
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=200505012041.j41KfFAA011729@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=cagney@gnu.org \
--cc=eliz@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