From: Giuliano Procida <gprocida@google.com>
To: libabigail@sourceware.org
Cc: dodji@seketeli.org, kernel-team@android.com, gprocida@google.com,
maennich@google.com
Subject: [PATCH 0/3] always create fresh corpus objects
Date: Tue, 27 Apr 2021 12:28:50 +0100 [thread overview]
Message-ID: <20210427112853.1338240-1-gprocida@google.com> (raw)
This is a small series of changes that adjust how corpus objects are
created when reading into a corpus group.
Overall the changes eliminate some conditional logic and make abidiff
slightly faster when processing ABIs containing multiple corpora.
Giuliano Procida (3):
abg-dwarf-reader: create new corpus unconditionally
abg-reader: ensure corpus always has a symtab reader
abg-reader: create a fresh corpus object per corpus
src/abg-dwarf-reader.cc | 9 +-----
src/abg-reader.cc | 71 +++++++++++------------------------------
2 files changed, 20 insertions(+), 60 deletions(-)
--
2.31.1.498.g6c1eba8ee3d-goog
next reply other threads:[~2021-04-27 11:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 11:28 Giuliano Procida [this message]
2021-04-27 11:28 ` [PATCH 1/3] abg-dwarf-reader: create new corpus unconditionally Giuliano Procida
2021-04-27 11:28 ` [PATCH 2/3] abg-reader: ensure corpus always has a symtab reader Giuliano Procida
2021-04-27 11:28 ` [PATCH 3/3] abg-reader: create a fresh corpus object per corpus Giuliano Procida
2021-06-10 16:54 ` Dodji Seketeli
2021-05-27 8:53 ` [PATCH v2 0/3] always create fresh corpus objects Giuliano Procida
2021-05-27 8:53 ` [PATCH v2 1/3] abg-dwarf-reader: create new corpus unconditionally Giuliano Procida
2021-06-01 7:38 ` Giuliano Procida
2021-06-10 15:58 ` [PATCH v2 1/3, applied] " Dodji Seketeli
2021-06-10 16:52 ` [PATCH v2 1/3] " Dodji Seketeli
2021-05-27 8:53 ` [PATCH v2 2/3] abg-reader: ensure corpus always has a symtab reader Giuliano Procida
2021-06-10 16:53 ` Dodji Seketeli
2021-05-27 8:53 ` [PATCH v2 3/3] abg-reader: create a fresh corpus object per corpus Giuliano Procida
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=20210427112853.1338240-1-gprocida@google.com \
--to=gprocida@google.com \
--cc=dodji@seketeli.org \
--cc=kernel-team@android.com \
--cc=libabigail@sourceware.org \
--cc=maennich@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).