From: "gprocida+abigail at google dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/26084] New: Misreporting of return type typedef differences in leaf mode
Date: Fri, 05 Jun 2020 08:24:08 +0000 [thread overview]
Message-ID: <bug-26084-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26084
Bug ID: 26084
Summary: Misreporting of return type typedef differences in
leaf mode
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: ---
Minimal case. Note that output is good in default reporting mode.
==> test-leaf1.0.cc <==
typedef int changed;
changed changed_fun() {
return 0;
}
==> test-leaf1.1.cc <==
typedef long changed;
changed changed_fun() {
return 0;
}
$ for i in 0 1; do gcc -g -Wall -Wextra -c test-leaf1.$i.cc -o test-leaf1.$i.o;
done
$ .../abidiff --leaf-changes-only test-leaf1.?.o
Leaf changes summary: 1 artifact changed
Changed leaf types summary: 0 leaf type changed
Removed/Changed/Added functions summary: 0 Removed, 1 Changed, 0 Added function
Removed/Changed/Added variables summary: 0 Removed, 0 Changed, 0 Added variable
1 function with some sub-type change:
[C] 'function changed changed_fun()' at test-leaf1.1.cc:3:1 has some sub-type
changes:
$
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-06-05 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 8:24 gprocida+abigail at google dot com [this message]
2020-09-16 15:57 ` [Bug default/26084] " dodji at redhat 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-26084-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).