From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/28675] New: whitespace in DWARF template naming confuses libabigail.
Date: Wed, 08 Dec 2021 23:44:04 +0000 [thread overview]
Message-ID: <bug-28675-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28675
Bug ID: 28675
Summary: whitespace in DWARF template naming confuses
libabigail.
Product: libabigail
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: woodard at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
Comparing gcc built libabigail.so.0 to llvm built libabigail.so.0 one of the
commonly reported differences is like this:
[C] 'method const std::vector<abigail::comparison::diff*,
std::allocator<abigail::comparison::diff*> >&
abigail::comparison::corpus_diff::children_nodes() const' at
abg-comparison.h:2325:1 has some indirect sub-type changes:
return type changed:
in referenced type 'const std::vector<abigail::comparison::diff*,
std::allocator<abigail::comparison::diff*> >':
'const std::vector<abigail::comparison::diff*,
std::allocator<abigail::comparison::diff*> >' changed to 'const
std::vector<abigail::comparison::diff *,
std::allocator<abigail::comparison::diff *> >'
The difference is nothing other than white space:
const std::vector<abigail::comparison::diff*,
std::allocator<abigail::comparison::diff*> >
const std::vector<abigail::comparison::diff *,
std::allocator<abigail::comparison::diff *> >
clang puts a space between typename and the * while GCC does not.
This should be a special case that is handled by libabigail. It is not an
actual ABI difference.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-12-08 23:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 23:44 woodard at redhat dot com [this message]
2021-12-08 23:44 ` [Bug default/28675] " woodard at redhat dot com
2021-12-09 0:10 ` woodard 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-28675-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).