From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org
Subject: [PATCH 0/3] Parse <elf.h> in the glibcelf Python module
Date: Mon, 05 Sep 2022 15:44:15 +0200 [thread overview]
Message-ID: <cover.1662385087.git.fweimer@redhat.com> (raw)
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.
Tested on i686-linux-gnu, x86-64-linux-gnu (the latter with Python 3.6
and Python 3.10). Build with build-many-glibcs.py.
Thanks,
Florian
Florian Weimer (3):
scripts: Extract glibcpp.py from check-obsolete-constructs.py
scripts: Enhance glibcpp to do basic macro processing
elf: Extract glibcelf constants from <elf.h>
elf/tst-glibcelf.py | 79 +-
scripts/check-obsolete-constructs.py | 189 +----
scripts/glibcelf.py | 1013 ++++++++++----------------
scripts/glibcpp.py | 529 ++++++++++++++
support/Makefile | 10 +-
support/tst-glibcpp.py | 217 ++++++
6 files changed, 1194 insertions(+), 843 deletions(-)
create mode 100644 scripts/glibcpp.py
create mode 100644 support/tst-glibcpp.py
base-commit: 29eb7961197bee68470730aecfdda4d0e206812e
--
2.37.2
next reply other threads:[~2022-09-05 13:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 13:44 Florian Weimer [this message]
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 ` [PATCH 0/3] Parse <elf.h> in the glibcelf Python module Florian Weimer
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=cover.1662385087.git.fweimer@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).