public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH 0/3] Parse <elf.h> in the glibcelf Python module
Date: Mon, 05 Sep 2022 16:36:16 +0200	[thread overview]
Message-ID: <875yi1c2hr.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <cover.1662385087.git.fweimer@redhat.com> (Florian Weimer via Libc-alpha's message of "Mon, 05 Sep 2022 15:44:15 +0200")

* Florian Weimer via Libc-alpha:

> This simplifies maintenance (backporting in particular), adds additional
> consistency checks (for otherwise-unused constants in <elf.h>), and
> should help with compatibility with earlier Python versions.
>
> If we want to use glibcelf more extensively in the test suite, I think
> we need to optimize the parser performance a bit.  The prefix matching
> is currently rather inefficient.  It should not be too hard to change
> that.

Actually, profiling suggests it's the C tokenizer. 8-/ That's going to
be more difficult to optimize.  It's still not too bad for now.

Thanks,
Florian


      parent reply	other threads:[~2022-09-05 14:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 13:44 Florian Weimer
2022-09-05 13:44 ` [PATCH 1/3] scripts: Extract glibcpp.py from check-obsolete-constructs.py Florian Weimer
2022-09-12 20:12   ` Siddhesh Poyarekar
2022-09-05 13:44 ` [PATCH 2/3] scripts: Enhance glibcpp to do basic macro processing Florian Weimer
2022-09-12 20:49   ` Siddhesh Poyarekar
2022-09-13  8:14     ` Florian Weimer
2022-09-05 13:44 ` [PATCH 3/3] elf: Extract glibcelf constants from <elf.h> Florian Weimer
2022-09-05 14:37   ` Florian Weimer
2022-09-13 17:34     ` Siddhesh Poyarekar
2022-09-14 10:06       ` Florian Weimer
2022-09-05 14:36 ` Florian Weimer [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:
  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=875yi1c2hr.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-alpha@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).