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: [RFC PATCH 0/3] Bug 26591 - tentative fix for some duplicate type ids
Date: Fri, 7 May 2021 19:42:47 +0100 [thread overview]
Message-ID: <20210507184250.3946416-1-gprocida@google.com> (raw)
This is RFC, because while this does fix some of the problems, there
may be unforseen consquences of the approach taken. Also, it has been
lightly tests (only on a subset of the test suite so far).
Comments welcome!
Giuliano Procida (3):
XML writer: treat function types more uniformly
XML writer: don't emit already emitted types
XML writer: emit enclosing types of scoped declarations
src/abg-writer.cc | 111 +-
.../data/test-annotate/test13-pr18894.so.abi | 298 +-
.../data/test-annotate/test14-pr18893.so.abi | 5516 +-
.../data/test-annotate/test15-pr18892.so.abi | 22297 +++----
.../data/test-annotate/test17-pr19027.so.abi | 38596 +++++------
...st18-pr19037-libvtkRenderingLIC-6.1.so.abi | 726 +-
...19-pr19023-libtcmalloc_and_profiler.so.abi | 9085 +--
...st20-pr19025-libvtkParallelCore-6.1.so.abi | 10103 +--
.../data/test-annotate/test21-pr19092.so.abi | 6549 +-
.../PR22015-libboost_iostreams.so.abi | 10 -
.../test-read-dwarf/PR22122-libftdc.so.abi | 5 -
.../PR25042-libgdbm-clang-dwarf5.so.6.0.0.abi | 395 +-
.../test-read-dwarf/PR26261/PR26261-exe.abi | 4 -
.../test-read-dwarf/test-libandroid.so.abi | 2818 +-
.../test-read-dwarf/test10-pr18818-gcc.so.abi | 25 -
.../test-read-dwarf/test12-pr18844.so.abi | 3881 +-
.../test-read-dwarf/test13-pr18894.so.abi | 184 +-
.../test-read-dwarf/test14-pr18893.so.abi | 3807 +-
.../test-read-dwarf/test15-pr18892.so.abi | 16117 ++---
.../test-read-dwarf/test16-pr18904.so.abi | 4862 +-
.../test-read-dwarf/test17-pr19027.so.abi | 12443 ++--
...st18-pr19037-libvtkRenderingLIC-6.1.so.abi | 428 -
...19-pr19023-libtcmalloc_and_profiler.so.abi | 6378 +-
...st20-pr19025-libvtkParallelCore-6.1.so.abi | 6329 +-
.../test-read-dwarf/test21-pr19092.so.abi | 3299 +-
.../test22-pr19097-libstdc++.so.6.0.17.so.abi | 53768 ++++++----------
.../test9-pr18818-clang.so.abi | 50 -
27 files changed, 74647 insertions(+), 133437 deletions(-)
--
2.31.1.607.g51e8a6a459-goog
next reply other threads:[~2021-05-07 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 18:42 Giuliano Procida [this message]
2021-05-07 18:42 ` [RFC PATCH 1/3] XML writer: treat function types more uniformly Giuliano Procida
2021-05-07 18:42 ` [RFC PATCH 2/3] XML writer: don't emit already emitted types Giuliano Procida
2021-05-07 18:42 ` [RFC PATCH 3/3] XML writer: emit enclosing types of scoped declarations 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=20210507184250.3946416-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).