public inbox for
 help / color / mirror / Atom feed
From: Tom Tromey <>
To: Joel Brobecker via Gdb-patches <>
Cc: Joel Brobecker <>
Subject: Re: GDB 13 release -- 2023-01-14 update
Date: Wed, 18 Jan 2023 11:49:17 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <Y8JSzhHjzfGMifa/> (Joel Brobecker via Gdb-patches's message of "Sat, 14 Jan 2023 10:59:26 +0400")

>>>>> "Joel" == Joel Brobecker via Gdb-patches <> writes:

Joel>   * [TomT] build/29966
Joel>     Cannot build anymore for win32 thread model of gdb

Joel>     Still assessing the impact of the issue described in the PR.
Joel>     I have a feeling that this is a corner case that shouldn't
Joel>     block the release, but double-checking on this.

There's another patch in the PR now; so if the original reporter tests
it, we can get it into GDB 13.  If not, we can just leave it as-is.

Joel>   * [TomT] c++/29896
Joel>     GDB git doesn't recognize template function name

Joel>     v2 Patch series posted at this location (2023-01-10),
Joel>     approved 2023-01-14:

I checked this in and Simon promptly reported it is broken.
I am investigating.

Joel>   * [Torbjorn] tdep/29738
Joel>     Arm M-profile dwarf2 unwinder performance suffers from exponential growth

Joel>     patch v2, 2022-11-18, reviewed 2022-11-21:

Joel>     Torbjorn mentioned that he's waiting for answers to questions
Joel>     he's asked from feedback received on one of the patches

I sent a review of the patch in question with some minor suggested


      parent reply	other threads:[~2023-01-18 18:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14  6:59 Joel Brobecker
2023-01-14 20:32 ` Tom Tromey
2023-01-18 18:49 ` Tom Tromey [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).