Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 17/17] MIPS support
Date: Wed, 17 Jul 2013 17:59:00 -0000	[thread overview]
Message-ID: <8738rdgj8p.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1372664545-3947-18-git-send-email-sergiodj@redhat.com> (Sergio	Durigan Junior's message of "Mon, 1 Jul 2013 04:42:25 -0300")

>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:

Sergio> MIPS already has a definition of its signals inside mips-linux-tdep.h
Sergio> (see enum mips_signals).  I could have used them, but I chose to
Sergio> follow the standard and implement an enum containing only differences
Sergio> between MIPS and x86 signals.  In the battle between code duplication
Sergio> and code standardization, the latter won (in my head, at least).  But I
Sergio> am totally open to suggestions, and I even believe I know what I will
Sergio> hear: "Please, use mips_signals".

Sergio> Anyway, I thought it was worth raising this point here.

Thanks.

One thing I'm curious about is why the corresponding
gdbarch_gdb_signal_from_target method is only implemented for MIPS, and
not for all Linux targets.

Consideration of this led me to another possible approach to the problem
you mention above: you could use your standard approach for the enum,
but also reimplement the MIPS gdbarch_gdb_signal_from_target method to
follow.  This would be simpler there was already a generic implementation...

Tom


  reply	other threads:[~2013-07-17 17:59 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01  7:43 [PATCH 00/17] Implement gdbarch_gdb_signal_to_target Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 09/17] i386 support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 08/17] h8300 support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 15/17] SPARC support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 14/17] s390 support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 13/17] mn10300 support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 11/17] m32r support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 05/17] ARM support Sergio Durigan Junior
2013-07-17 17:20   ` Tom Tromey
2013-07-25  6:25     ` Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 02/17] Linux kernel generic support Sergio Durigan Junior
2013-07-01 10:57   ` Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 10/17] IA-64 support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 07/17] Cris support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 16/17] Xtensa support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 06/17] AVR support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 04/17] x86_64 support Sergio Durigan Junior
2013-07-17 17:16   ` Tom Tromey
2013-07-17 19:00     ` Mark Kettenis
2013-07-17 19:11     ` Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 03/17] Alpha support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 01/17] Implement the gdbarch.{sh,c,h} bits Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 17/17] MIPS support Sergio Durigan Junior
2013-07-17 17:59   ` Tom Tromey [this message]
2013-07-25  6:20     ` Sergio Durigan Junior
2013-07-29 20:15       ` Pedro Alves
2013-07-01  7:43 ` [PATCH 12/17] m68klinux support Sergio Durigan Junior
2013-07-01  8:43 ` [PATCH 00/17] Implement gdbarch_gdb_signal_to_target Andreas Schwab
2013-07-01 10:40   ` Sergio Durigan Junior
2013-07-01 10:44     ` Pedro Alves
2013-07-01 10:59       ` Sergio Durigan Junior
2013-07-01 10:46 ` [PATCH 18/18] AArch64 support Sergio Durigan Junior
2013-07-08 23:08 ` [ping][PATCH 00/17] Implement gdbarch_gdb_signal_to_target Sergio Durigan Junior
2013-07-17 18:02 ` [PATCH " Tom Tromey

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=8738rdgj8p.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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