From: Luis Machado <luis.machado@arm.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: GDB 14 branching & release -- 2023-09-30 update
Date: Mon, 2 Oct 2023 14:48:04 +0100 [thread overview]
Message-ID: <7753b523-e642-fc60-bae9-0ce472edbf66@arm.com> (raw)
In-Reply-To: <ZRi6wwHDmzzntBoC@adacore.com>
Hi Joel,
On 10/1/23 01:18, Joel Brobecker via Gdb-patches wrote:
> Hi everyone,
>
> Here is a quick update compared to last week. Depending on how gdb/30689
> goes, I am hoping we might be able to branch this coming weekend.
I think we have reached an agreement. I'll push both series as soon as the pre-requisite
patch goes in.
>
> Fixed Since the Previous Update:
> --------------------------------
>
> * [TomT]
> Add pretty-printer base class and new methods
> https://sourceware.org/pipermail/gdb-patches/2023-September/202342.html
>
> Added Since the Last Update:
> ----------------------------
>
> * [SimonM] PR gdb/30912
> Regression: make check TESTS="gdb.base/gcore.exp" RUNTESTFLAGS="--target_board=native-extended-gdbserver"
> https://sourceware.org/bugzilla/show_bug.cgi?id=30912
>
> (not blocking for branching)
>
> 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 v7 series (Sep 18):
> https://sourceware.org/pipermail/gdb-patches/2023-September/202581.html
>
> SME2 v5 series (Sep 13):
> https://sourceware.org/pipermail/gdb-patches/2023-September/202597.html
>
> Not Blocking, But Keep An Eye On:
> ---------------------------------
>
> < none >
>
> Fingers crossed :-).
next prev parent reply other threads:[~2023-10-02 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 0:18 Joel Brobecker
2023-10-02 13:48 ` Luis Machado [this message]
2023-10-06 13:30 ` Joel Brobecker
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=7753b523-e642-fc60-bae9-0ce472edbf66@arm.com \
--to=luis.machado@arm.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).