public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org
Subject: [PATCH v2 0/3] Parse <elf.h> in the glibcelf Python module
Date: Wed, 14 Sep 2022 16:59:52 +0200	[thread overview]
Message-ID: <cover.1663167514.git.fweimer@redhat.com> (raw)

This version addresses Siddhesh's review comments and adds a check that
the prefix filter actually matches anything.

Tested on i686-linux-gnu and x86_64-linux-gnu.

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                  | 1016 ++++++++++----------------
 scripts/glibcpp.py                   |  529 ++++++++++++++
 support/Makefile                     |   10 +-
 support/tst-glibcpp.py               |  217 ++++++
 6 files changed, 1197 insertions(+), 843 deletions(-)
 create mode 100644 scripts/glibcpp.py
 create mode 100644 support/tst-glibcpp.py


base-commit: 05967faf0e3df6aad07f0b05e138e86f82363deb
-- 
2.37.2


             reply	other threads:[~2022-09-14 14:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14 14:59 Florian Weimer [this message]
2022-09-14 14:59 ` [PATCH v2 1/3] scripts: Extract glibcpp.py from check-obsolete-constructs.py Florian Weimer
2022-09-14 15:00 ` [PATCH v2 2/3] scripts: Enhance glibcpp to do basic macro processing Florian Weimer
2022-09-21 17:08   ` Siddhesh Poyarekar
2022-09-14 15:00 ` [PATCH v2 3/3] elf: Extract glibcelf constants from <elf.h> Florian Weimer
2022-09-21 18:05   ` Siddhesh Poyarekar

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.1663167514.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).