From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/28760] New: libstdc++ doesn't pass self check
Date: Tue, 11 Jan 2022 01:55:15 +0000 [thread overview]
Message-ID: <bug-28760-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28760
Bug ID: 28760
Summary: libstdc++ doesn't pass self check
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: ---
With the latest trunk as of: 71633a7c0c7c96c03db8c18826afea26da0f7b4b we get
problems with libstdc++ from libstdc++-11.2.1-7.fc35.x86_64
$ abidw --abidiff /lib64/libstdc++.so.6.0.29
Functions changes summary: 0 Removed, 0 Changed (2 filtered out), 0 Added
functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
]$ echo $?
1
$ abidw /lib64/libstdc++.so.6.0.29 >/tmp/a.abixml
$ abidiff /tmp/a.abixml /lib64/libstdc++.so.6.0.29
Functions changes summary: 0 Removed, 0 Changed (2 filtered out), 0 Added
functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
$ abidiff --harmless /tmp/a.abixml /lib64/libstdc++.so.6.0.29
Functions changes summary: 0 Removed, 2 Changed, 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
2 functions with some indirect sub-type change:
[C] 'method virtual std::__codecvt_abstract_base<char16_t, char8_t,
__mbstate_t>::result std::codecvt<char16_t, char8_t,
__mbstate_t>::do_unshift(std::codecvt<char16_t, char8_t,
__mbstate_t>::state_type&, std::codecvt<char16_t, char8_t,
__mbstate_t>::extern_type*, std::codecvt<char16_t, char8_t,
__mbstate_t>::extern_type*, std::codecvt<char16_t, char8_t,
__mbstate_t>::extern_type*&) const' at codecvt.cc:914:1 has some indirect
sub-type changes:
Please note that the symbol of this function is
_ZNKSt7codecvtIDsDu11__mbstate_tE10do_unshiftERS0_PDuS3_RS3_@@GLIBCXX_3.4.26
and it aliases symbol:
_ZNKSt7codecvtIDiDu11__mbstate_tE10do_unshiftERS0_PDuS3_RS3_@@GLIBCXX_3.4.26
return type changed:
entity changed from 'typedef std::__codecvt_abstract_base<char16_t,
char8_t, __mbstate_t>::result' to compatible type 'enum
std::codecvt_base::result' at codecvt.h:52:1
[C] 'method virtual std::__codecvt_abstract_base<char32_t, char8_t,
__mbstate_t>::result std::codecvt<char32_t, char8_t,
__mbstate_t>::do_unshift(std::codecvt<char32_t, char8_t,
__mbstate_t>::state_type&, std::codecvt<char32_t, char8_t,
__mbstate_t>::extern_type*, std::codecvt<char32_t, char8_t,
__mbstate_t>::extern_type*, std::codecvt<char32_t, char8_t,
__mbstate_t>::extern_type*&) const' at codecvt.cc:990:1 has some indirect
sub-type changes:
Please note that the exported symbol of this function is
_ZNKSt7codecvtIDiDu11__mbstate_tE10do_unshiftERS0_PDuS3_RS3_@@GLIBCXX_3.4.26
return type changed:
entity changed from 'typedef std::__codecvt_abstract_base<char32_t,
char8_t, __mbstate_t>::result' to compatible type 'enum
std::codecvt_base::result' at codecvt.h:52:1
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-01-11 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 1:55 woodard at redhat dot com [this message]
2022-01-11 1:56 ` [Bug default/28760] " woodard at redhat dot com
2022-06-28 22:55 ` 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-28760-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).