From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29303] Unacceptable performance doing fedabipkgdiff on some packages
Date: Tue, 12 Jul 2022 15:55:59 +0000 [thread overview]
Message-ID: <bug-29303-9487-yEHf7ev0H0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29303-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29303
dodji at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |29360
--- Comment #4 from dodji at redhat dot com ---
So, the fedabipkgdiff --self-compare -a --from fc36 zlib-ada one appears to be
due to a lack of support for the "range type", in Ada. That is what leads to
an infinite loop, sadly.
I have filed a separate tracking bug for it at #29360. Also, I have started
the work on that in the branch
https://sourceware.org/git/?p=libabigail.git;a=shortlog;h=refs/heads/free-range-types.
The current status of that branch transforms the infinite loop into an assert
now, at least. Maybe we could just merge it as is, for now, I am not sure.
As this is a lower priority, I'll move to looking into more pressing stuff.
This is however a nice little project of its own to work on, maybe for someone
who would like to get into libabigail hacking? ;-)
Referenced Bugs:
https://sourceware.org/bugzilla/show_bug.cgi?id=29360
[Bug 29360] Ada ranges emitting/reading/diffing are not supported in libabigail
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-12 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 1:07 [Bug default/29303] New: " woodard at redhat dot com
2022-06-30 1:07 ` [Bug default/29303] " woodard at redhat dot com
2022-06-30 12:44 ` dodji at redhat dot com
2022-06-30 12:54 ` dodji at redhat dot com
2022-07-05 23:15 ` woodard at redhat dot com
2022-07-07 13:58 ` woodard at redhat dot com
2022-07-12 15:55 ` dodji at redhat dot com [this message]
2022-07-12 15:56 ` dodji at redhat dot com
2022-07-28 23:44 ` woodard at redhat dot com
2023-04-06 11:21 ` 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-29303-9487-yEHf7ev0H0@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).