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 5/7] SPARC support
Date: Sat, 27 Jul 2013 17:13:00 -0000 [thread overview]
Message-ID: <CADPb22THztNL-gNozoq3H+Sy6dT+usMtLAMjZah5TTebQ2Rv8A@mail.gmail.com> (raw)
In-Reply-To: <1374869594-16965-6-git-send-email-sergiodj@redhat.com>
Hi. Just a nit.
On Fri, Jul 26, 2013 at 1:13 PM, Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
> Support for SPARC. It does not share some signal numbers, therefore
> there is the target-specific implementation for them.
>
> 2013-07-26 Sergio Durigan Junior <sergiodj@redhat.com>
>
> * sparc-linux-tdep.c: Define enum with differences between SPARC
> and x86 signal numbers.
> (sparc32_linux_gdb_signal_from_target): New function.
> (sparc32_linux_gdb_signal_to_target): Likewise.
> (sparc32_linux_init_abi): Set gdbarch_gdb_signal_{to,from}_target
> to the functions defined above.
> [...]
> @@ -267,6 +292,113 @@ sparc32_linux_get_syscall_number (struct gdbarch *gdbarch,
>
> return ret;
> }
Nit: Missing blank line here.
> +/* Implementation of `gdbarch_gdb_signal_from_target', as defined in
> + gdbarch.h. */
> +
> +static enum gdb_signal
> +sparc32_linux_gdb_signal_from_target (struct gdbarch *gdbarch,
> + int signal)
> +{
> [...]
next prev parent reply other threads:[~2013-07-27 17:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 20:13 [PATCH 0/7] Implement gdbarch_gdb_signal_{to,from}_target 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 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 [this message]
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
2013-07-29 16:43 ` Pedro Alves
2013-08-09 16:56 ` Sergio Durigan Junior
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=CADPb22THztNL-gNozoq3H+Sy6dT+usMtLAMjZah5TTebQ2Rv8A@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