From: "gprocida+abigail at google dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27554] New: abidw emits unreachable types and declarations
Date: Tue, 09 Mar 2021 23:22:51 +0000 [thread overview]
Message-ID: <bug-27554-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27554
Bug ID: 27554
Summary: abidw emits unreachable types and declarations
Product: libabigail
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: gprocida+abigail at google dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
A fairly common thing to do is to expose C bindings only, even if a library is
written in C++ (or some other language).
We noticed that ABI XML contains all (or at least very many) of the C++
declarations and their type dependencies found in the DWARF, even if none of
these contribute to the ABI of such a library.
For one AOSP library, a rough analysis I did suggested that of the 153358 types
emitted in the XML, only 103 of them are reachable from the exported library
symbols. Similarly, there are 15261 declarations with mangled-name attributes,
but only 66 exported symbols. There are clearly massive space savings possible.
Dodji, do you think this would be a lot of work to implement within libabigail
itself?
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-03-09 23:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 23:22 gprocida+abigail at google dot com [this message]
2021-03-09 23:30 ` [Bug default/27554] " gprocida+abigail at google dot com
2021-03-16 17:17 ` gprocida+abigail at google dot com
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=bug-27554-9487@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@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).