From: Alan Hayward <Alan.Hayward@arm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
Sergio Durigan Junior <sergiodj@redhat.com>,
Andrew Burgess <andrew.burgess@embecosm.com>,
"GDB Patches" <gdb-patches@sourceware.org>, nd <nd@arm.com>
Subject: Re: GDB 8.2 branch 2018-06-11 Update
Date: Tue, 12 Jun 2018 08:29:00 -0000 [thread overview]
Message-ID: <0B648932-A474-461D-8CD8-41189FE3A19F@arm.com> (raw)
In-Reply-To: <20180611225629.GA31935@adacore.com>
(Resending without email disclaimer)
> On 11 Jun 2018, at 23:56, Joel Brobecker <brobecker@adacore.com> wrote:
>
> Hello everyone,
>
> I hinted in a message I sent a couple of weeks ago on this mailing-list
> (https://www.sourceware.org/ml/gdb-patches/2018-05/msg00821.html),
> we should be getting ready for the next GDB release branch (8.2).
>
> So far, I have received the following requests. I tried to find
> relevant URLs whenever possible, but please update me if you have
> a better one.
>
> * (AlanH) gdb/gdbserver support for aarch64 SVE
> [v2] https://www.sourceware.org/ml/gdb-patches/2018-06/msg00145.html
>
> * (PhilippeW) Implement 'frame apply COMMAND', enhance 'thread apply COMMAND'
> [v2] https://www.sourceware.org/ml/gdb-patches/2018-06/msg00118.html
>
> * (SergioDJ) Implement IPv6 support for GDB/gdbserver
> Latest update: received comments, waiting for new version:
> https://www.sourceware.org/ml/gdb-patches/2018-06/msg00238.html
>
> * (AndrewB) gdb: Don't drop SIGSTOP during stop_all_threads
> Latest update: Reviewed and mostly OK'ed (minor comments)
> Waiting for next version of the patch.
> https://www.sourceware.org/ml/gdb-patches/2018-06/msg00284.html
>
> I would like very much to cut the branch by end of this month at
> the very latest. After that, we get into the summer holidays where
> things start getting slow, so I'd rather start before then.
>
> Do you guys think you'll be able to make it?
>
> --
> Joel
Most of the SVE patches are in now. I’ve just got four remaining:
[PATCH v2 02/10] Add Aarch64 SVE Linux headers
https://sourceware.org/ml/gdb-patches/2018-06/msg00220.html
- Simon wanted to check with FSF people if it’s ok to include Linux headers.
[PATCH v2 05/10] Ptrace support for Aarch64 SVE
https://sourceware.org/ml/gdb-patches/2018-06/msg00262.html
- Okayed (with nit changes). Commit blocked on 02/10
[PATCH v2 09/10] Ptrace support for AArch64 SVE gdbsever
https://sourceware.org/ml/gdb-patches/2018-06/msg00270.html
- I need to respond. However, this will still be blocked on 02/10
[PATCH] Support large registers in regcache transfer_regset
https://sourceware.org/ml/gdb-patches/2018-06/msg00303.html
- New. Replacement for 10/10. Requires review.
Assuming 2/10 gets okayed, this should all get done this week.
Thanks,
Alan.
next prev parent reply other threads:[~2018-06-12 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 22:56 Joel Brobecker
2018-06-12 0:19 ` Sergio Durigan Junior
2018-06-12 8:29 ` Alan Hayward [this message]
2018-06-12 12:59 ` Simon Marchi
2018-06-12 21:57 ` Philippe Waroquiers
2018-06-19 6:07 ` Tom Tromey
2018-06-22 14:21 ` Joel Brobecker
2018-06-22 20:37 ` 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=0B648932-A474-461D-8CD8-41189FE3A19F@arm.com \
--to=alan.hayward@arm.com \
--cc=andrew.burgess@embecosm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=philippe.waroquiers@skynet.be \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).