Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Vrany <jan@vrany.io>
To: gdb-patches@sourceware.org
Cc: Jan Vrany <jan@vrany.io>
Subject: [PATCH v3 0/7] Remove addrmap from blockvector
Date: Wed, 22 Apr 2026 10:29:37 +0000	[thread overview]
Message-ID: <20260422102923.1185738-1-jan@vrany.io> (raw)
In-Reply-To: <20260304165914.3209106-1-jan.vrany@labware.com>

This is a v3 of an earlier series removing the addrmap from blockvector, a
step towards expandable blockvectors which are needed for lazy CU expansion
and forPython JIT API.

Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=33829

* v1 submission is here:

  https://inbox.sourceware.org/gdb-patches/20260219185638.360694-1-jan.vrany@labware.com/

* v2 submission is here:

  https://inbox.sourceware.org/gdb-patches/20260304165914.3209106-1-jan.vrany@labware.com/

* changes since v3:

  * rebased on current master to accomodate changes in expanded_symbols_functions

  * re-tested on Linux x86_64 both with and without -readnow. I have spotted
    no regressions, but I need to say that on my machine and with my test
    setup a lot of tests fail with -readnow.

Thanks!

Jan

---

Jan Vrany (7):
  gdb: implement readnow_functions::find_pc_sect_compunit_symtab
  gdb: update expanded_symbols_functions::find_pc_sect_compunit_symtab
  gdb: simplify find_compunit_symtab_for_pc_sect
  gdb: update blockvector::lookup to handle non-contiguous blocks
  gdb: do not set blockvector address map
  gdb: remove address map from struct blockvector
  gdb: add unit test for blockvector::lookup of non-contiguous blocks

 gdb/block-selftests.c | 156 +++++++++++++++++++++++++-----------------
 gdb/block.c           |  34 ++++++---
 gdb/block.h           |  17 ++---
 gdb/buildsym.c        |  55 +--------------
 gdb/dwarf2/read.c     |  73 +++++++++++++++++---
 gdb/expanded-symbol.c |  18 +++++
 gdb/expanded-symbol.h |   8 +--
 gdb/symtab.c          |  91 ------------------------
 8 files changed, 206 insertions(+), 246 deletions(-)

-- 
2.53.0



  parent reply	other threads:[~2026-04-22 10:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 16:59 [PATCH v2 " Jan Vrany
2026-03-04 16:59 ` [PATCH v2 1/7] gdb: implement readnow_functions::find_pc_sect_compunit_symtab Jan Vrany
2026-03-04 16:59 ` [PATCH v2 2/7] gdb: update expanded_symbols_functions::find_pc_sect_compunit_symtab Jan Vrany
2026-03-04 21:19   ` Tom Tromey
2026-03-04 16:59 ` [PATCH v2 3/7] gdb: simplify find_compunit_symtab_for_pc_sect Jan Vrany
2026-03-04 16:59 ` [PATCH v2 4/7] gdb: update blockvector::lookup to handle non-contiguous blocks Jan Vrany
2026-03-04 16:59 ` [PATCH v2 5/7] gdb: do not set blockvector address map Jan Vrany
2026-03-04 16:59 ` [PATCH v2 6/7] gdb: remove address map from struct blockvector Jan Vrany
2026-03-04 16:59 ` [PATCH v2 7/7] gdb: add unit test for blockvector::lookup of non-contiguous blocks Jan Vrany
2026-03-10 18:14 ` [PING] Re: [PATCH v2 0/7] Remove addrmap from blockvector Jan Vraný
2026-04-22 10:29 ` Jan Vrany [this message]
2026-04-28 18:55   ` [PING] Re: [PATCH v3 " Jan Vrany
2026-05-08  9:14   ` Jan Vrany
2026-04-22 10:29 ` [PATCH v3 1/7] gdb: implement readnow_functions::find_pc_sect_compunit_symtab Jan Vrany
2026-04-22 10:29 ` [PATCH v3 2/7] gdb: update expanded_symbols_functions::find_pc_sect_compunit_symtab Jan Vrany
2026-04-22 10:29 ` [PATCH v3 3/7] gdb: simplify find_compunit_symtab_for_pc_sect Jan Vrany
2026-04-22 10:30 ` [PATCH v3 4/7] gdb: update blockvector::lookup to handle non-contiguous blocks Jan Vrany
2026-04-22 10:30 ` [PATCH v3 5/7] gdb: do not set blockvector address map Jan Vrany
2026-04-22 10:30 ` [PATCH v3 6/7] gdb: remove address map from struct blockvector Jan Vrany
2026-04-22 10:30 ` [PATCH v3 7/7] gdb: add unit test for blockvector::lookup of non-contiguous blocks Jan Vrany

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=20260422102923.1185738-1-jan@vrany.io \
    --to=jan@vrany.io \
    --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