public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29693] New: clang-libs from f37 fails self test with 2.1
Date: Fri, 14 Oct 2022 22:14:43 +0000	[thread overview]
Message-ID: <bug-29693-9487@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29693

            Bug ID: 29693
           Summary: clang-libs from f37 fails self test with 2.1
           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: ---

This is an interesting one because it is both an assert and a bad comparison.
It also doesn't seem to fall in with any of the other bad comparisons or
asserts.

The impacted library is libclang-cpp.so.15 so this is a library issue.


$ fedabipkgdiff --self-compare -a --from fc37 clang-libs
Comparing the ABI of binaries between clang-libs-15.0.0-2.fc37.aarch64.rpm and
clang-libs-15.0.0-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.0' ====

Comparing the ABI of binaries between clang-devel-15.0.0-2.fc37.aarch64.rpm and
clang-devel-15.0.0-2.fc37.aarch64.rpm:

==== SELF CHECK SUCCEEDED for 'clang-tblgen' ====

Comparing the ABI of binaries between clang-libs-15.0.0-2.fc37.i686.rpm and
clang-libs-15.0.0-2.fc37.i686.rpm:

==== SELF CHECK SUCCEEDED for 'libclang-cpp.so.15' ====
==== SELF CHECK SUCCEEDED for 'libclang.so.15.0.0' ====

Comparing the ABI of binaries between clang-devel-15.0.0-2.fc37.i686.rpm and
clang-devel-15.0.0-2.fc37.i686.rpm:

==== SELF CHECK SUCCEEDED for 'clang-tblgen' ====

Comparing the ABI of binaries between clang-libs-15.0.0-2.fc37.ppc64le.rpm and
clang-libs-15.0.0-2.fc37.ppc64le.rpm:

==== SELF CHECK SUCCEEDED for 'libclang-cpp.so.15' ====
==== SELF CHECK SUCCEEDED for 'libclang.so.15.0.0' ====

Comparing the ABI of binaries between clang-devel-15.0.0-2.fc37.ppc64le.rpm and
clang-devel-15.0.0-2.fc37.ppc64le.rpm:

==== SELF CHECK SUCCEEDED for 'clang-tblgen' ====

Comparing the ABI of binaries between clang-libs-15.0.0-2.fc37.s390x.rpm and
clang-libs-15.0.0-2.fc37.s390x.rpm:

==== SELF CHECK SUCCEEDED for 'libclang-cpp.so.15' ====
==== SELF CHECK SUCCEEDED for 'libclang.so.15.0.0' ====

Comparing the ABI of binaries between clang-devel-15.0.0-2.fc37.s390x.rpm and
clang-devel-15.0.0-2.fc37.s390x.rpm:

==== SELF CHECK SUCCEEDED for 'clang-tblgen' ====

Comparing the ABI of binaries between clang-devel-15.0.0-2.fc37.x86_64.rpm and
clang-devel-15.0.0-2.fc37.x86_64.rpm:

==== SELF CHECK SUCCEEDED for 'clang-tblgen' ====

Comparing the ABI of binaries between clang-libs-15.0.0-2.fc37.x86_64.rpm and
clang-libs-15.0.0-2.fc37.x86_64.rpm:

abipkgdiff: ../../../libabigail/src/abg-default-reporter.cc:375: virtual void
abigail::comparison::default_reporter::report(const
abigail::comparison::qualified_type_diff&, std::ostream&, const std::string&)
const: Assertion `__abg_cond__' failed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-10-14 22:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 22:14 woodard at redhat dot com [this message]
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
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@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).