[v2,0/4] Fix regression in new DWARF reader

Message ID	20230110183338.2623088-1-tromey@adacore.com
Headers	DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 1B2733858D33 To: gdb-patches@sourceware.org Subject: [PATCH v2 0/4] Fix regression in new DWARF reader Date: Tue, 10 Jan 2023 11:33:34 -0700 Message-Id: <20230110183338.2623088-1-tromey@adacore.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: list From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> Reply-To: Tom Tromey <tromey@adacore.com> Errors-To: gdb-patches-bounces+patchwork=sourceware.org@sourceware.org Sender: "Gdb-patches" <gdb-patches-bounces+patchwork=sourceware.org@sourceware.org>
Series	Fix regression in new DWARF reader \| [v2,0/4] Fix regression in new DWARF reader [v2,1/4] Avoid submitting empty tasks in parallel_for_each [v2,2/4] Don't erase empty indices in DWARF reader [v2,3/4] Move hash_entry and eq_entry into cooked_index::do_finalize [v2,4/4] Fix parameter-less template regression in new DWARF reader

Message ID

20230110183338.2623088-1-tromey@adacore.com

Headers

DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 1B2733858D33
To: gdb-patches@sourceware.org
Subject: [PATCH v2 0/4] Fix regression in new DWARF reader
Date: Tue, 10 Jan 2023 11:33:34 -0700
Message-Id: <20230110183338.2623088-1-tromey@adacore.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: list
From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Reply-To: Tom Tromey <tromey@adacore.com>
Errors-To: gdb-patches-bounces+patchwork=sourceware.org@sourceware.org
Sender: "Gdb-patches"
 <gdb-patches-bounces+patchwork=sourceware.org@sourceware.org>

Series

Fix regression in new DWARF reader |

Message

Tom Tromey Jan. 10, 2023, 6:33 p.m. UTC

  Here's v2 of the series to fix a regression introduced by the new
DWARF reader.

v1 was here:

    https://sourceware.org/pipermail/gdb-patches/2022-December/194795.html

In this version, I added some unit tests in patch #1 to try to
demonstrate that patch #2 is safe.  Because parallel_for_each is now
so complicated, this turns out to be non-obvious, and in fact I found
another bug (not affecting patch #2 -- the bug was that an empty task
could still be submitted -- but an empty task does not yield an empty
result) in it while working on this.

Let me know what you think.  This is blocking GDB 13.

Tom