From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: RFC: mips-linux software single step versus sigreturn
Date: Sun, 03 Apr 2005 21:35:00 -0000 [thread overview]
Message-ID: <20050403213503.GA20654@nevyn.them.org> (raw)
In-Reply-To: <200504031918.j33JIOIV016132@elgar.sibelius.xs4all.nl>
On Sun, Apr 03, 2005 at 09:18:24PM +0200, Mark Kettenis wrote:
> Date: Sat, 2 Apr 2005 23:25:54 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> Any comments?
>
> Is the extra indirection via os_methods really necessary?
I'm not thrilled with it either, but when Andrew maintained the MIPS
port, he expressed opposition to moving MIPS's gdbarch_tdep to
mips-tdep.h. The original patch was here:
http://sources.redhat.com/ml/gdb-patches/2002-10/msg00119.html
The objection was here:
http://sources.redhat.com/ml/gdb-patches/2002-11/msg00038.html
If the consensus has swung the other way, I'll revise...
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-04-03 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-03 4:26 Daniel Jacobowitz
2005-04-03 19:18 ` Mark Kettenis
2005-04-03 21:35 ` Daniel Jacobowitz [this message]
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=20050403213503.GA20654@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.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