From: "dodji at seketeli dot org" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29047] abidiff statistics omit symbol with no debug info changes
Date: Wed, 01 Jun 2022 16:20:42 +0000 [thread overview]
Message-ID: <bug-29047-9487-pycWUC2XdE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29047-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29047
--- Comment #1 from dodji at seketeli dot org ---
gprocida at google dot com via Libabigail <libabigail@sourceware.org> a
écrit:
> Leaf changes summary: 510 artifacts changed
> Changed leaf types summary: 0 leaf type changed
> Removed/Changed/Added functions summary: 0 Removed, 0 Changed, 499 Added
> functions
> Removed/Changed/Added variables summary: 0 Removed, 0 Changed, 11 Added
> variables
> Function symbols changes summary: 0 Removed, 0 Added function symbol not
> referenced by debug info
> Variable symbols changes summary: 0 Removed, 3 Added variable symbols not
> referenced by debug info
>
> 510 = 499 + 11
> but should be
> 513 = 499 + 11 + 3
Thank you for reporting this issue.
I posted a patch for this to
https://sourceware.org/pipermail/libabigail/2022q2/004385.html.
Do you see an improvement with that patch at all?
Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-06-01 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 15:43 [Bug default/29047] New: " gprocida at google dot com
2022-06-01 16:20 ` Dodji Seketeli
2022-06-01 16:20 ` dodji at seketeli dot org [this message]
2022-06-02 8:48 ` [Bug default/29047] " gprocida at google dot com
2022-06-02 15:00 ` Dodji Seketeli
2022-06-02 15:00 ` dodji at seketeli dot org
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-29047-9487-pycWUC2XdE@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).