From: "gprocida+abigail at google dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27278] New: Stray non-diff
Date: Fri, 29 Jan 2021 16:45:06 +0000 [thread overview]
Message-ID: <bug-27278-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27278
Bug ID: 27278
Summary: Stray non-diff
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: ---
Created attachment 13175
--> https://sourceware.org/bugzilla/attachment.cgi?id=13175&action=edit
input XML files
Hi.
Here is an instance where abidiff thinks there is a change, but doesn't have
anything to say. There may be something not quite right in how things are
labelled as harmless. Interestingly, the output looks more correct with
--leaf-changes-only.
I'm afraid I don't have a small test case. This is at current master,
40709acdd5189e473f27cd8626d6023d6bdf6d8d.
$ abidiff --leaf-changes-only /tmp/{a,b}.xml
Leaf changes summary: 0 artifact changed (80 filtered out)
Changed leaf types summary: 0 (80 filtered out) leaf types changed
Removed/Changed/Added functions summary: 0 Removed, 0 Changed, 0 Added function
Removed/Changed/Added variables summary: 0 Removed, 0 Changed, 0 Added variable
$ build/tools/abidiff /tmp/{a,b}.xml
Functions changes summary: 0 Removed, 2 Changed (3373 filtered out), 0 Added
functions
Variables changes summary: 0 Removed, 0 Changed (78 filtered out), 0 Added
variables
2 functions with some indirect sub-type change:
[C] 'function bool drm_dp_mst_allocate_vcpi(drm_dp_mst_topology_mgr*,
drm_dp_mst_port*, int, int)' at drm_dp_mst_topology.c:0:0 has some indirect
sub-type changes:
parameter 2 of type 'drm_dp_mst_port*' has sub-type changes:
in pointed to type 'struct drm_dp_mst_port' at drm_dp_mst_helper.h:0:0:
type size hasn't changed
no data member changes (5 filtered);
[C] 'function void drm_dp_mst_deallocate_vcpi(drm_dp_mst_topology_mgr*,
drm_dp_mst_port*)' at drm_dp_mst_topology.c:0:0 has some indirect sub-type
changes:
parameter 2 of type 'drm_dp_mst_port*' has sub-type changes:
pointed to type 'struct drm_dp_mst_port' changed at
drm_dp_mst_helper.h:0:0, as reported earlier
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-01-29 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 16:45 gprocida+abigail at google dot com [this message]
2021-02-01 14:22 ` [Bug default/27278] " gprocida+abigail at google dot com
2021-04-13 9:52 ` gprocida+abigail at google dot com
2021-05-11 10:13 ` gprocida+abigail at google dot com
2021-07-26 15:57 ` gprocida 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-27278-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).