From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: mark.kettenis@xs4all.nl, gdb-patches@sources.redhat.com
Subject: Re: [commit] Use bfd_byte in value.h
Date: Sun, 01 May 2005 21:13:00 -0000 [thread overview]
Message-ID: <01c54e92$Blat.v2.4$5cf24460@zahav.net.il> (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>
> CC: mark.kettenis@xs4all.nl, gdb-patches@sources.redhat.com
>
> Eli,
>
> Last time this came up I recommeded separating out the idea of gdb_byte
> and proposed more formally. How is this going?
Sorry, I'm not sure I understand (or maybe I forgot). Can you please
point me to the message with your proposal?
> 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.
I'd rather discuss first and decide, then implement. This way, you
won't need to s/bfd_byte/gdb_byte/, however trivial. The discussion
should not last long enough to delay the solution for GCC 4: after
all, it seems like a very simple issue. With any luck, we could agree
on something in a day or two.
next prev parent reply other threads:[~2005-05-01 21:13 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
2005-05-01 21:13 ` Eli Zaretskii [this message]
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='01c54e92$Blat.v2.4$5cf24460@zahav.net.il' \
--to=eliz@gnu.org \
--cc=cagney@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