From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: GDB 13 release -- 2023-01-14 update
Date: Sat, 14 Jan 2023 10:59:26 +0400 [thread overview]
Message-ID: <Y8JSzhHjzfGMifa/@adacore.com> (raw)
Hi everyone,
I think we're getting closer to our first pre-release, but sadly,
we're still not there yet. Here is an updated status since last week:
Fixed Since the Previous Update:
--------------------------------
< none - we almost had build/29966, but oh well ;-) >
Added Since the Last Update:
----------------------------
* [TomT] build/29966
Cannot build anymore for win32 thread model of gdb
https://sourceware.org/bugzilla/show_bug.cgi?id=29966
Still assessing the impact of the issue described in the PR.
I have a feeling that this is a corner case that shouldn't
block the release, but double-checking on this.
Other Ongoing Items:
--------------------
* [TomT] c++/29896
GDB git doesn't recognize template function name
https://sourceware.org/bugzilla/show_bug.cgi?id=29896
v2 Patch series posted at this location (2023-01-10),
approved 2023-01-14:
https://sourceware.org/pipermail/gdb-patches/2023-January/195537.html
* [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
Torbjorn mentioned that he's waiting for answers to questions
he's asked from feedback received on one of the patches
https://sourceware.org/pipermail/gdb-patches/2023-January/195378.html
Cheers,
--
Joel
next reply other threads:[~2023-01-14 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 6:59 Joel Brobecker [this message]
2023-01-14 20:32 ` Tom Tromey
2023-01-18 18:49 ` Tom Tromey
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=Y8JSzhHjzfGMifa/@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).