From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
To: Joel Brobecker <brobecker@adacore.com>, <gdb-patches@sourceware.org>
Subject: Re: GDB 13 release -- 2023-01-21 Update
Date: Wed, 25 Jan 2023 21:18:54 +0100 [thread overview]
Message-ID: <95dc547e-59f8-95b3-903c-138d8842cea0@foss.st.com> (raw)
In-Reply-To: <Y8uBaiybGp8lWmIr@adacore.com>
On 2023-01-21 07:08, Joel Brobecker via Gdb-patches wrote:
> Hi everyone,
>
> Quick update for the past week: We've inching closer, but we still
> have one leftover regression which I think we should wait for before
> we create the first pre-release. Kudos to Tom for his persistence
> in hardening the new parallel DWARF reader.
>
> Here is an updated status since last week:
>
> Fixed Since the Previous Update:
> --------------------------------
>
> < none >
>
> 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, reviewed 2023-01-20:
> https://sourceware.org/pipermail/gdb-patches/2023-January/195915.html
I just pushed this for master.
Is it okay to also push the 2 patches to gdb-13-branch?
Kind regards,
Torbjörn
>
> Not Blocking, But Keep An Eye On:
> ---------------------------------
>
> * [TomT] build/29966
> Cannot build anymore for win32 thread model of gdb
> https://sourceware.org/bugzilla/show_bug.cgi?id=29966
>
next prev parent reply other threads:[~2023-01-25 20:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 6:08 Joel Brobecker
2023-01-25 20:18 ` Torbjorn SVENSSON [this message]
2023-01-27 6:30 ` Joel Brobecker
2023-01-27 6:38 ` Luis Machado
2023-01-27 17:17 ` Simon Marchi
2023-01-28 8:39 ` Luis Machado
2023-01-29 11:52 ` Joel Brobecker
2023-01-30 11:23 ` Luis Machado
2023-01-31 7:03 ` Joel Brobecker
2023-01-31 13:57 ` Luis Machado
2023-01-31 14:33 ` Luis Machado
2023-02-02 3:44 ` 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=95dc547e-59f8-95b3-903c-138d8842cea0@foss.st.com \
--to=torbjorn.svensson@foss.st.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).