Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Sergio Durigan Junior <sergiodj@redhat.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: Sat, 27 Jul 2013 17:57:00 -0000	[thread overview]
Message-ID: <CADPb22QyKksran=OhgOq4A=ULU6xWuoPxY_ZEHWffRDU_oVeGg@mail.gmail.com> (raw)
In-Reply-To: <1374869594-16965-1-git-send-email-sergiodj@redhat.com>

On Fri, Jul 26, 2013 at 1:13 PM, Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
> This is the second attempt to implement gdbarch_gdb_signal_to_target,
> but this time with the additional implementation of
> gdbarch_gdb_signal_from_target (a MIPS-only method so far).
>
> The first attempt is here:
>
> <http://sourceware.org/ml/gdb-patches/2013-07/msg00002.html>
>
> The notable changes are:
>
> - linux-tdep.c now registers the generic converters itself, thus
>   eliminating the need for every target to do so.
>
> - Comment about SIGSWI on ARM (discussion here:
>   <http://sourceware.org/ml/gdb-patches/2013-07/msg00002.html>).
>
> - Rewrite MIPS implementation of gdbarch_gdb_signal_from_target.
>   Remove "enum mips_signals".
>
> Hopefully everything is right now.  If the patch is approved, I intend
> to commit it as a whole, instead of each chunk separately.
>
> Thanks.

Hi.

I reviewed all the patches.
Except for a few nits pointed out in some of the patches, the set is ok with me.
As a sanity check, did you do an enable-targets=all build?
[modulo I didn't audit the signal lists and values]
Also, you may wish to leave it a few days in case others wish to comment.

I gather there is a use for gdbarch_gdb_signal_to_target coming, so no
worries there.

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.

[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.]


  parent reply	other threads:[~2013-07-27 17:57 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 1/7] Implement the gdbarch.{sh,c,h} bits Sergio Durigan Junior
2013-07-26 20:13 ` [PATCH 2/7] Linux kernel generic support Sergio Durigan Junior
2013-07-26 20:13 ` [PATCH 6/7] Xtensa support 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-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 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 5/7] SPARC support Sergio Durigan Junior
2013-07-27 17:13   ` Doug Evans
2013-08-07 21:03     ` Sergio Durigan Junior
2013-07-27 17:57 ` Doug Evans [this message]
2013-08-07 20:54   ` [PATCH 0/7] Implement gdbarch_gdb_signal_{to,from}_target Sergio Durigan Junior
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='CADPb22QyKksran=OhgOq4A=ULU6xWuoPxY_ZEHWffRDU_oVeGg@mail.gmail.com' \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@redhat.com \
    --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