From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Doug Evans <dje@google.com>
Cc: GDB Patches <gdb-patches@sourceware.org>, Tom Tromey <tromey@redhat.com>
Subject: Re: [PATCH 0/7] Implement gdbarch_gdb_signal_{to,from}_target
Date: Wed, 07 Aug 2013 20:54:00 -0000 [thread overview]
Message-ID: <m3li4d1asv.fsf@redhat.com> (raw)
In-Reply-To: <CADPb22QyKksran=OhgOq4A=ULU6xWuoPxY_ZEHWffRDU_oVeGg@mail.gmail.com> (Doug Evans's message of "Sat, 27 Jul 2013 10:57:38 -0700")
On Saturday, July 27 2013, Doug Evans wrote:
> Hi.
Hi. Sorry for the delay.
> I reviewed all the patches.
> Except for a few nits pointed out in some of the patches, the set is
> ok with me.
Thanks.
> As a sanity check, did you do an enable-targets=all build?
Yes, I always build my patches this way :-).
> I gather there is a use for gdbarch_gdb_signal_to_target coming, so no
> worries there.
Yep.
> In older times one couldn't use "signal" as a variable name to avoid a
> possible collision with a system header defining a macro signal. I
> see record-full.c uses "signal" so perhaps we no longer have to deal
> with that, but heads up.
Hm, I wasn't aware of such constraint. Anyway, since there is a
precedence, then I won't bother changing.
> [fwiw, and this is just a side discussion, not meant to block the
> patch or anything ...
> This is an example of the kind of thing that I wish existed in a
> library anyone could use.
> Yeah, we're converting to/from GDB_FOO, but I can imagine it being
> useful to multiple tools.]
Sounds nice, indeed. Weekend project, maybe? :-).
--
Sergio
next prev parent reply other threads:[~2013-08-07 20:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 20:13 Sergio Durigan Junior
2013-07-26 20:13 ` [PATCH 2/7] Linux kernel generic support Sergio Durigan Junior
2013-07-26 20:13 ` [PATCH 1/7] Implement the gdbarch.{sh,c,h} bits Sergio Durigan Junior
2013-07-26 20:13 ` [PATCH 6/7] Xtensa support Sergio Durigan Junior
2013-07-26 20:13 ` [PATCH 3/7] Alpha support Sergio Durigan Junior
2013-07-29 16:44 ` Pedro Alves
2013-08-07 21:09 ` Sergio Durigan Junior
2013-08-08 15:44 ` Pedro Alves
2013-07-26 20:13 ` [PATCH 7/7] MIPS support Sergio Durigan Junior
2013-07-27 17:22 ` Doug Evans
2013-08-07 21:02 ` Sergio Durigan Junior
2013-07-26 20:13 ` [PATCH 5/7] SPARC support Sergio Durigan Junior
2013-07-27 17:13 ` Doug Evans
2013-08-07 21:03 ` Sergio Durigan Junior
2013-07-26 20:13 ` [PATCH 4/7] AVR support Sergio Durigan Junior
2013-07-27 17:10 ` Doug Evans
2013-08-07 21:03 ` Sergio Durigan Junior
2013-07-27 17:57 ` [PATCH 0/7] Implement gdbarch_gdb_signal_{to,from}_target Doug Evans
2013-08-07 20:54 ` Sergio Durigan Junior [this message]
2013-07-29 16:43 ` Pedro Alves
2013-08-09 16:56 ` Sergio Durigan Junior
2013-08-11 1:49 Joern Rennecke
2013-08-12 3:51 ` Sergio Durigan Junior
2013-08-12 8:48 ` Joern Rennecke
2013-08-12 11:07 ` Pedro Alves
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=m3li4d1asv.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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