From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: GDB 13 release -- 2022-12-18 update
Date: Sun, 18 Dec 2022 12:39:05 +0400 [thread overview]
Message-ID: <Y57RqS1cjuGDCgEJ@adacore.com> (raw)
Hello everyone,
The gdb-13-branch has been created!
Unlike more times, I haven't generated a pre-release yet, because
we have a couple of known issues (See "Added Since the Last Update")
with pending patches where I think it would be better if we wanted
until there were both backported before we did send out the first
pre-release. Hopefully soon!
As always, for the .1 release, any patch approved for backporting
by a Global Maintainer can be cherry-picked on the gdb-13-branch.
In the meantime, below is a more detailed update.
Fixed Since the Previous Update:
--------------------------------
* [TomT] Windows target-async interrupt
Added Since the Last Update:
----------------------------
* [TomT] c++/29896
GDB git doesn't recognize template function name
https://sourceware.org/bugzilla/show_bug.cgi?id=29896
Patch series posted at this location (2022-12-15):
https://sourceware.org/pipermail/gdb-patches/2022-December/194795.html
* [EliZ]
GDB build issues when mingw.org's version of MinGW
https://sourceware.org/pipermail/gdb-patches/2022-December/194894.html
Other Ongoing Items:
--------------------
* [Torbjorn] tdep/29738
Arm M-profile dwarf2 unwinder performance suffers from exponential growth
https://sourceware.org/bugzilla/show_bug.cgi?id=29738
patch v2, 2022-11-18, reviewed 2022-11-21:
https://sourceware.org/pipermail/gdb-patches/2022-November/193960.html
Aside from an email on Dec 8th, I don't see any updates on this one.
--
Joel
reply other threads:[~2022-12-18 8:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Y57RqS1cjuGDCgEJ@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).