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 7/7] MIPS support
Date: Wed, 07 Aug 2013 21:02:00 -0000 [thread overview]
Message-ID: <m3haf11afm.fsf@redhat.com> (raw)
In-Reply-To: <CADPb22SxVOtmTh=Eg9DrNYb50SWKT-0_NdeDUD8BjTq7TgPuUw@mail.gmail.com> (Doug Evans's message of "Sat, 27 Jul 2013 10:22:19 -0700")
On Saturday, July 27 2013, Doug Evans wrote:
> Hi. Just a nit.
>
> On Fri, Jul 26, 2013 at 1:13 PM, Sergio Durigan Junior
> <sergiodj@redhat.com> wrote:
>> Support for the MIPS target. MIPS already had a definition of
>> gdbarch_gdb_signal_from_target, and also an enum containing all signal
>> numbers from this target. So, in order to make things standard, I
>> removed the previous enum in favor of the new, difference-only enum
>> declared by this patch series. And I also redefined the implementation
>> of gdbarch_gdb_signal_from_target for MIPS in order to take this new
>> enum into account, and only handle the signals which are different from
>> the Linux kernel generic ones.
>>
>> 2013-07-26 Sergio Durigan Junior <sergiodj@redhat.com>
>>
>> * mips-linux-tdep.c: Define enum with differences between
>> signals in MIPS and Linux kernel generic ones.
>> (mips_gdb_signal_to_target): New function.
>> (mips_gdb_signal_from_target): Redefine to use new enum, handle
>> only different signals from the Linux kernel generic.
>> (mips_linux_init_abi): Set gdbarch_gdb_signal_{to,from}_target
>> the functions defined above.
>> * mips_gdb_signal_to_target (enum mips_signals): Remove.
>
> Nit: Fix changelog entry for mips-linux-tdep.h.
Done, thanks.
--
Sergio
next prev parent reply other threads:[~2013-08-07 21:02 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 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 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 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 7/7] MIPS support Sergio Durigan Junior
2013-07-27 17:22 ` Doug Evans
2013-08-07 21:02 ` Sergio Durigan Junior [this message]
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-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=m3haf11afm.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