From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29672] New: gcc from Fedora 37 asserts fedabipkgdiff --self-compare
Date: Tue, 11 Oct 2022 22:12:58 +0000 [thread overview]
Message-ID: <bug-29672-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29672
Bug ID: 29672
Summary: gcc from Fedora 37 asserts fedabipkgdiff
--self-compare
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 of libabigail as of
4c5f44473e9f7c0a561174fdc6cc89f40dd9892a
gcc asserts with:
abipkgdiff: ../../../libabigail/src/abg-ir-priv.h:687: void
abigail::ir::environment::priv::pop_composite_type_comparison_operands(const
abigail::ir::type_base*, const abigail::ir::type_base*): Assertion
`__abg_cond__' failed.
The location of this assertion appears to be different than
https://sourceware.org/bugzilla/show_bug.cgi?id=28301 but the sourcecode has
changed so much it might be related.
edabipkgdiff --self-compare -a --from fc37 gcc
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-10-11 22:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 22:12 woodard at redhat dot com [this message]
2022-10-11 22:14 ` [Bug default/29672] " woodard at redhat dot com
2022-10-14 16:33 ` woodard at redhat dot com
2022-12-16 20:08 ` woodard at redhat dot com
2023-03-23 23:13 ` 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-29672-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).