From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29912] New: smesh fails self compare on x86_64
Date: Fri, 16 Dec 2022 21:27:51 +0000 [thread overview]
Message-ID: <bug-29912-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29912
Bug ID: 29912
Summary: smesh fails self compare on x86_64
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: ---
fedabipkgdiff --self-compare -a --from fc37 smesh
fails self compare. This problem probably existed in 2.1 but wasn't isolated.
However it continues to present in 2.2 trunk as of 1f51b9e8
Comparing the ABI of binaries between smesh-9.8.0.2-2.fc37.x86_64.rpm and
smesh-9.8.0.2-2.fc37.x86_64.rpm:
======== comparing'libnglib4smesh.so' to itself wrongly yielded result:
===========
Functions changes summary: 0 Removed, 1 Changed, 0 Added function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
1 function with some indirect sub-type change:
[C] 'method virtual const netgen::GeomPoint<3>&
netgen::LineSeg<3>::StartPI() const' at spline.hpp:213:1 has some indirect
sub-type changes:
Please note that the symbol of this function is
_ZNK6netgen10SplineSeg3ILi2EE7StartPIEv
and it aliases symbol: _ZNK6netgen10SplineSeg3ILi3EE7StartPIEv
'method virtual const netgen::GeomPoint<3>& netgen::LineSeg<3>::StartPI()
const {_ZNK6netgen10SplineSeg3ILi2EE7StartPIEv,
_ZNK6netgen10SplineSeg3ILi3EE7StartPIEv}' now becomes 'method virtual const
netgen::GeomPoint<2>& netgen::SplineSeg3<2>::StartPI() const
{_ZNK6netgen10SplineSeg3ILi2EE7StartPIEv,
_ZNK6netgen10SplineSeg3ILi3EE7StartPIEv}'
return type changed:
in referenced type 'const netgen::GeomPoint<3>':
'const netgen::GeomPoint<3>' changed to 'const netgen::GeomPoint<2>'
implicit parameter 0 of type 'const netgen::LineSeg<3>*' changed:
in pointed to type 'const netgen::LineSeg<3>':
'const netgen::LineSeg<3>' changed to 'const netgen::SplineSeg3<2>'
The types that it is confusing are particularly weird.
It only seems to happen on x86_64 all the other architectures seem to compare
properly.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-12-16 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 21:27 woodard at redhat dot com [this message]
2022-12-16 21:28 ` [Bug default/29912] " woodard at redhat dot com
2023-01-07 0:56 ` woodard at redhat dot com
2023-03-20 21:16 ` dodji at redhat dot com
2023-03-20 21:18 ` dodji at redhat dot com
2023-03-21 10:36 ` 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-29912-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).