From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29912] smesh fails self compare on x86_64
Date: Mon, 20 Mar 2023 21:16:57 +0000 [thread overview]
Message-ID: <bug-29912-9487-k1nrJBBJKf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29912-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29912
dodji at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #2 from dodji at redhat dot com ---
(In reply to Ben Woodard from comment #0)
> 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:
I could indeed see this, thanks.
I think I have a fix for this issue which I have committed at
https://sourceware.org/git/?p=libabigail.git;a=commit;h=b987db9bcbdc1bcccd52b6b44399d4e9de038975.
[...]
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-20 21:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 21:27 [Bug default/29912] New: " woodard at redhat dot com
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 [this message]
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-k1nrJBBJKf@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).