From: Alan Hayward <Alan.Hayward@arm.com>
To: Tom Tromey <tom@tromey.com>
Cc: "gdb-patches\\@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: [RFC 0/2] Let's discuss moving gdbserver to top-level
Date: Mon, 03 Jun 2019 10:24:00 -0000 [thread overview]
Message-ID: <995AED5B-1925-48A1-BA22-3735E6CFABE7@arm.com> (raw)
In-Reply-To: <20190530213046.20542-1-tom@tromey.com>
> On 30 May 2019, at 22:30, Tom Tromey <tom@tromey.com> wrote:
>
> I've wanted to move gdbserver to the top-level for a while now. I
> think it will provide a decent benefit, mainly by letting gdb and
> gdbserver share their libiberty, gnulib, and "common" libraries --
> shaving off some build time. It also will have the nice side effect
> of simplifying gdbserver's Makefile, fixing some existing bugs.
>
> I have written the patches to do this, but before reworking them into
> submittable form, I thought I'd send a couple of initial patches and
> start a discussion.
>
> This short series removes a couple of barriers to turning "common"
> into a library. These are pretty much the only changes that could be
> sent in isolation.
>
> The rest of the series is:
>
> * Move gnulib to the top-level
> * Rename "common" to "gdbsupport" in preparation for a move
> * Move "gdbsupport" to top-level
> * Move gdbserver to top-level
> * Make gdbserver share the other top-level libraries
>
> Most of the patches are pretty mechanical. There are one or two
> hacks, primarily because this series doesn't move the "nat" directory.
>
> Let me know what you think.
Do you have a work in progress branch you could push? I think it’d be
Useful to see what things look like after all the changes.
>
> Tom
>
>
next prev parent reply other threads:[~2019-06-03 10:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 21:30 Tom Tromey
2019-05-30 21:30 ` [RFC 1/2] Remove linux-waitpid.c debugging code Tom Tromey
2019-06-03 14:57 ` Simon Marchi
2019-06-03 16:32 ` Tom Tromey
2019-06-05 9:32 ` Pedro Alves
2019-05-30 21:30 ` [RFC 2/2] Move gdb's xmalloc and friends to new file Tom Tromey
2019-06-03 15:03 ` Simon Marchi
2019-06-03 16:33 ` Tom Tromey
2019-06-05 9:40 ` Pedro Alves
2019-06-05 22:33 ` Tom Tromey
2019-06-17 15:45 ` Alan Hayward
2019-06-17 17:43 ` Tom Tromey
2019-06-17 18:37 ` Pedro Alves
2019-06-18 9:31 ` Alan Hayward
2019-07-03 16:18 ` Alan Hayward
2019-07-13 16:04 ` Tom Tromey
2019-07-16 19:47 ` Pedro Alves
2019-06-03 10:24 ` Alan Hayward [this message]
2019-06-03 13:13 ` [RFC 0/2] Let's discuss moving gdbserver to top-level Tom Tromey
2019-06-03 14:27 ` Simon Marchi
2019-06-03 16:30 ` Tom Tromey
2019-06-05 9:16 ` Pedro Alves
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=995AED5B-1925-48A1-BA22-3735E6CFABE7@arm.com \
--to=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).