From: Pedro Alves <palves@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>, jhb@freebsd.org
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] Add fbsd_nat_add_target.
Date: Tue, 28 Apr 2015 01:08:00 -0000 [thread overview]
Message-ID: <553EAEBF.2030406@redhat.com> (raw)
In-Reply-To: <201504272050.t3RKoCSV018211@glazunov.sibelius.xs4all.nl>
On 04/27/2015 09:50 PM, Mark Kettenis wrote:
>> From: John Baldwin <jhb@freebsd.org>
>> Date: Mon, 27 Apr 2015 16:17:52 -0400
>> FWIW, obsd-nat.c (which I have looked at a bit), also uses a wrapper
>> around add_target rather than creating a generic OpenBSD native target.
>> To change the FreeBSD native targets I think would be an invasive change
>> since they use platform-specific native targets that are pan-BSD as their
>> initial target (e.g. amd64bsd_target) and customize from there. To make
>> fbsd_nat_target work I would need to rework things like amd64bsd_target
>> to modify an existing target instead of returning a new one I think (which
>> would also mean changing all the other BSD native targets).
>
> Which is why I'm perfectly happy with your current 1/3 diff ;).
I'm happy with it too. I was just curious.
Sounds like we'll need to revisit this if/when we make target_ops a
proper class hierarchy, but we'll cross that bridge when we come to it.
> As far as I'm concerned you're the expert here and to me the series
> looks reasonable as posted.
Agreed.
Thanks,
Pedro Alves
prev parent reply other threads:[~2015-04-27 21:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-26 1:25 John Baldwin
2015-04-27 19:24 ` Pedro Alves
2015-04-27 19:27 ` John Baldwin
2015-04-27 20:26 ` Mark Kettenis
2015-04-27 20:36 ` John Baldwin
2015-04-28 1:06 ` Mark Kettenis
2015-04-28 1:08 ` Pedro Alves [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=553EAEBF.2030406@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.org \
--cc=mark.kettenis@xs4all.nl \
/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