From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29693] clang-libs from f37 fails self test with 2.1
Date: Fri, 24 Mar 2023 16:20:10 +0000 [thread overview]
Message-ID: <bug-29693-9487-Vgy4dBMPL0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29693-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29693
--- Comment #4 from Ben Woodard <woodard at redhat dot com> ---
The fedabipkgdiff on clang-libs ran all night without making any apparent
forward progress. So it appears like we have two bugs here.
1) what is causing fedabipkgdiff to spin in what appears to be an infinite loop
after doing at least some of the abipkgdiff comparisons.
2) clang-libs is failing selfcheck when run at a basic abipkgdiff level.
$ abipkgdiff --self-check --d1
/home/ben/.cache/fedabipkgdiff/downloads/clang-devel-debuginfo-15.0.7-2.fc37.aarch64.rpm
--d1
/home/ben/.cache/fedabipkgdiff/downloads/clang-libs-debuginfo-15.0.7-2.fc37.aarch64.rpm
--d1
/home/ben/.cache/fedabipkgdiff/downloads/clang-tools-extra-debuginfo-15.0.7-2.fc37.aarch64.rpm
--d1
/home/ben/.cache/fedabipkgdiff/downloads/clang-debuginfo-15.0.7-2.fc37.aarch64.rpm
/home/ben/.cache/fedabipkgdiff/downloads/clang-libs-15.0.7-2.fc37.aarch64.rpm
======== comparing'libclang-cpp.so.15' to itself wrongly yielded result:
===========
Functions changes summary: 0 Removed, 1 Changed (1 filtered out), 0 Added
functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
1 function with some indirect sub-type change:
[C] 'method virtual clang::dataflow::Solver::Result
clang::dataflow::WatchedLiteralsSolver::solve(llvm::DenseSet<clang::dataflow::BoolValue
*, llvm::DenseMapInfo<clang::dataflow::BoolValue *, void> >)' at
WatchedLiteralsSolver.h:31:1 has some indirect sub-type changes:
return type changed:
type size hasn't changed
2 data member deletions:
'clang::dataflow::Solver::Result::Status SATCheckStatus', at offset 0
(in bits) at Solver.h:78:1
'llvm::Optional<llvm::DenseMap<clang::dataflow::AtomicBoolValue *,
clang::dataflow::Solver::Result::Assignment,
llvm::DenseMapInfo<clang::dataflow::AtomicBoolValue *, void>,
llvm::detail::DenseMapPair<clang::dataflow::AtomicBoolValue *,
clang::dataflow::Solver::Result::Assignment> > > Solution', at offset 64 (in
bits) at Solver.h:79:1
===SELF CHECK FAILED for 'libclang-cpp.so.15'
==== SELF CHECK SUCCEEDED for 'libclang.so.15.0.7' ====
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-24 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 22:14 [Bug default/29693] New: " woodard at redhat dot com
2022-10-14 22:15 ` [Bug default/29693] " woodard at redhat dot com
2022-10-25 17:01 ` woodard at redhat dot com
2023-03-23 21:13 ` woodard at redhat dot com
2023-03-23 23:41 ` woodard at redhat dot com
2023-03-24 16:20 ` woodard at redhat dot com [this message]
2023-03-31 22:46 ` [Bug default/29693] clang-libs from f37 fails self test with pre-2.3 trunk woodard at redhat dot com
2023-04-11 14:51 ` dodji at redhat dot com
2023-05-17 15: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-29693-9487-Vgy4dBMPL0@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).