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] Tidy some peeling code
Date: Thu, 9 Jul 2020 14:14:26 +0100 [thread overview]
Message-ID: <20200709131429.1366074-1-gprocida@google.com> (raw)
Hi Dodji.
This is a short series of very small clean-ups. All the changes relate
to helper functions that peel off some of the outer layers of a type
to see what might be inside.
There may be an opportunity to tighten up the checks being done in
functions like maybe_canonicalize_type and
types_have_similar_structure which are typical users of these helpers.
Regards,
Giuliano.
Giuliano Procida (3):
abg-comparison.h: Remove stray declaration
Remove unused is_reference_or_pointer_diff.
Simplify peel_typedef_pointer_or_reference_type
include/abg-comparison.h | 5 -----
include/abg-fwd.h | 6 ++----
src/abg-comp-filter.cc | 6 ++----
src/abg-comparison.cc | 15 ---------------
src/abg-dwarf-reader.cc | 6 ++----
src/abg-ir.cc | 40 +++++++++-------------------------------
6 files changed, 15 insertions(+), 63 deletions(-)
--
2.27.0.383.g050319c2ae-goog
next reply other threads:[~2020-07-09 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 13:14 Giuliano Procida [this message]
2020-07-09 13:14 ` [PATCH 1/3] abg-comparison.h: Remove stray declaration Giuliano Procida
2020-07-10 16:16 ` Matthias Maennich
2020-07-27 13:27 ` Dodji Seketeli
2020-07-09 13:14 ` [PATCH 2/3] Remove unused is_reference_or_pointer_diff Giuliano Procida
2020-07-10 16:16 ` Matthias Maennich
2020-07-27 13:28 ` Dodji Seketeli
2020-07-09 13:14 ` [PATCH 3/3] Simplify peel_typedef_pointer_or_reference_type Giuliano Procida
2020-07-10 16:17 ` Matthias Maennich
2020-07-27 13:28 ` Dodji Seketeli
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=20200709131429.1366074-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).