From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: GDB 14 branching & release -- 2023-09-16 update
Date: Sat, 16 Sep 2023 07:02:38 -0700 [thread overview]
Message-ID: <ZQW1fgfcFufwYNZg@adacore.com> (raw)
Hi everyone,
My sincere apologies for the long period of radio silence since
the last update. It's been a busy summer :-/.
Here is a quick status of what has been discussed so far. In short,
we're down to one PR for AArch64, which has been progress (new patch
series posted a few days ago). Are there other issues that we should
fix before we branch?
Otherwise, let's branch soon :-).
More detailed update:
Fixed Since the Previous Update:
--------------------------------
* [JohnB] Handle variable XSAVE layouts
https://sourceware.org/pipermail/gdb-patches/2023-July/200895.html
* [JohnB] Fixes for multiprocess for FreeBSD's native target
(v2) https://sourceware.org/pipermail/gdb-patches/2023-July/200962.html
Added Since the Last Update:
----------------------------
< none >
Other Ongoing Items:
--------------------
* [LuisM] PR gdb/30689
[AArch64] gdb scalable matrix extension (SME1 and SME2) support
https://sourceware.org/bugzilla/show_bug.cgi?id=30689
SME1 v6 series (Sep 13):
https://sourceware.org/pipermail/gdb-patches/2023-September/202418.html
SME2 v4 series (Sep 13):
https://sourceware.org/pipermail/gdb-patches/2023-September/202425.html
Not Blocking, But Keep An Eye On:
---------------------------------
< none >
Thank you!
--
Joel
next reply other threads:[~2023-09-16 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 14:02 Joel Brobecker [this message]
2023-09-18 18:29 ` Tom Tromey
2023-09-18 20:02 ` Tom Tromey
2023-09-18 21:32 ` Luis Machado
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=ZQW1fgfcFufwYNZg@adacore.com \
--to=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).