From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29407] New: arm-none-eabi-gcc-cs fails self-check
Date: Mon, 25 Jul 2022 21:47:48 +0000 [thread overview]
Message-ID: <bug-29407-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29407
Bug ID: 29407
Summary: arm-none-eabi-gcc-cs fails self-check
Product: libabigail
Version: unspecified
Status: NEW
Severity: minor
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: woodard at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
Created attachment 14232
--> https://sourceware.org/bugzilla/attachment.cgi?id=14232&action=edit
output with errors
$ fedabipkgdiff --self-compare -a --from fc36 arm-none-eabi-gcc-cs fails with
a huge number of errors.
This is with the most latest trunk as of:
7513a91ff03148efebd5b68ff776b5ddd1e3af4f
The output is quite long and is not like anything that I've seen before. It
seems to have a lot to do with virtual functions.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-07-25 21:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 21:47 woodard at redhat dot com [this message]
2022-07-26 20:04 ` [Bug default/29407] " woodard at redhat dot com
2022-07-27 2:22 ` woodard at redhat dot com
2022-10-14 16:31 ` [Bug default/29407] kdepim-addons " woodard at redhat dot com
2022-10-14 16:48 ` woodard at redhat dot com
2022-10-14 16:52 ` woodard at redhat dot com
2022-10-14 18:29 ` woodard at redhat dot com
2023-03-23 22:32 ` woodard at redhat dot com
2023-03-23 22:33 ` [Bug default/29407] kscope " woodard at redhat dot com
2023-03-23 22:37 ` woodard at redhat dot com
2023-05-18 19:11 ` 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-29407-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).