From: Simon Marchi <simon.marchi@polymtl.ca>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 8.2 branch 2018-06-22 Update
Date: Fri, 22 Jun 2018 14:10:00 -0000 [thread overview]
Message-ID: <213286bb97dd6bfa9cb5deb51ef2867b@polymtl.ca> (raw)
In-Reply-To: <20180622140540.GC3128@adacore.com>
On 2018-06-22 10:05, Joel Brobecker wrote:
> Hi everyone,
>
> Can we do a quick status update on the branch? Below are items that
> were discussed previously. For those items that are still in progress,
> can you tell us whether or not you think you'll be able to finish it
> by end of this month?
>
> Note that, for practical reasons, the window for branching is either
> end of this month, or end of July.
>
> As far as I know, the following items are now complete:
>
> * (AlanH) gdb/gdbserver support for aarch64 SVE
> Looks like the code is now in? :-)
>
> [v3]
> https://www.sourceware.org/ml/gdb-patches/2018-06/msg00400.html
> [v2]
> https://www.sourceware.org/ml/gdb-patches/2018-06/msg00145.html
Yes I think this is done.
> * (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
This looks like it's in too.
Simon
next prev parent reply other threads:[~2018-06-22 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 14:05 Joel Brobecker
2018-06-22 14:10 ` Simon Marchi [this message]
2018-06-22 14:13 ` Joel Brobecker
[not found] ` <87fu1eep8o.fsf@redhat.com>
2018-06-22 18:22 ` Joel Brobecker
2018-06-22 20:41 ` Sergio Durigan Junior
2018-06-23 15:17 ` Philippe Waroquiers
2018-06-25 21:26 ` Pedro Franco de Carvalho
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=213286bb97dd6bfa9cb5deb51ef2867b@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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