From: "Jan Vraný" <Jan.Vrany@labware.com>
To: "tom@tromey.com" <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] gdb/jit: add function symbols to global block
Date: Tue, 13 Jan 2026 21:42:51 +0000 [thread overview]
Message-ID: <79227e4c024aad95b42c70022093c917ace6f6dd.camel@labware.com> (raw)
In-Reply-To: <87a4yhjxgj.fsf@tromey.com>
On Tue, 2026-01-13 at 09:20 -0700, Tom Tromey wrote:
> > > > > > "Jan" == Jan Vrany <jan.vrany@labware.com> writes:
>
> Jan> + {
> Jan> + new_block = new (&objfile->objfile_obstack) global_block;
> Jan> + new_block->set_multidict (
> Jan> + mdict_create_linear (&objfile->objfile_obstack, global_symbols));
> Jan> + }
> Jan> else
> Jan> - new_block = new (&objfile->objfile_obstack) block;
> Jan> + {
> Jan> + new_block = new (&objfile->objfile_obstack) block;
> Jan> + new_block->set_multidict (
> Jan> + mdict_create_linear (&objfile->objfile_obstack, {}));
> Jan> + }
>
> Does anything ever get added to the static block?
No (at the moment).
> If not then making a dictionary doesn't seem necessary?
As the code stands now, I think it has to - the rest of code expects it is
always there. For example, blockvector::~blockvector() just unconditionally
frees the dictionary. Or blpy_repr() that calls mdict_size().
>
> Also the formatting is wonky here, that "(" should not be at the end of
> the line. (Two instances of this.)
Sorry, will fix that.
Jan
>
> Kind of weird that this code doesn't use buildsym, but OTOH buildsym is
> horrible.
>
> Tom
next prev parent reply other threads:[~2026-01-13 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 18:15 Jan Vrany
2026-01-13 16:20 ` Tom Tromey
2026-01-13 21:42 ` Jan Vraný [this message]
2026-01-13 22:47 ` Tom Tromey
2026-01-14 10:44 ` [PATCH v3] " Jan Vrany
2026-01-14 13:42 ` 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=79227e4c024aad95b42c70022093c917ace6f6dd.camel@labware.com \
--to=jan.vrany@labware.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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