From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: GDB 13 release -- 2023-01-29 Update
Date: Sun, 29 Jan 2023 15:58:17 +0400 [thread overview]
Message-ID: <Y9ZfWZGHpkjH+Z2i@adacore.com> (raw)
Hi everyone,
Quick update: We have progress on one of the issues (tdep/29738)
which makes me think that we'll be down to one single issue before
we make our first pre-release.
Below is a more detailed status:
Fixed Since the Previous Update:
--------------------------------
* [TomT] build/29966
Cannot build anymore for win32 thread model of gdb
https://sourceware.org/bugzilla/show_bug.cgi?id=29966
This ticket got closed, and then reopened I am not sure by whom,
probably the author. I don't believe there is anything there
for us to do, so moving this to the "fixed" section.
Added Since the Last Update:
----------------------------
< none >
Other Ongoing Items:
--------------------
* [TomT] c++/29896
GDB git doesn't recognize template function name
https://sourceware.org/bugzilla/show_bug.cgi?id=29896
Patches pushed, to both master and branch, but unfortunately
a regression was found - Tom confirmed and is working on a fix.
https://sourceware.org/pipermail/gdb-patches/2023-January/195828.html
* [Torbjorn] tdep/29738
Arm M-profile dwarf2 unwinder performance suffers from exponential growth
https://sourceware.org/bugzilla/show_bug.cgi?id=29738
patch v3, 2023-01-19 has been pushed!
https://sourceware.org/pipermail/gdb-patches/2023-January/195915.html
Backporting has been approved, waiting for it to be done.
Not Blocking, But Keep An Eye On:
---------------------------------
< none >
--
Joel
next reply other threads:[~2023-01-30 5:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 11:58 Joel Brobecker [this message]
2023-01-30 18:54 ` Tom Tromey
2023-01-31 7:25 ` 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=Y9ZfWZGHpkjH+Z2i@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).