From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/31313] infinitish run for abidw on libgs-9.27-1.el8.x86_64.rpm /usr/lib64/libgs.so.9.27
Date: Wed, 14 Feb 2024 13:51:46 +0000 [thread overview]
Message-ID: <bug-31313-9487-GSqr4W5QM4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31313-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31313
dodji at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #2 from dodji at redhat dot com ---
Hello,
I could reproduce the issue, thanks for reporting the issue.
This appears to be one these embarrassing quadratic behaviour that the current
type canonicalization process has :-(
I tried the work-in-progress type-hashing branch on the binary and here is what
I am getting:
$ time ~/git/libabigail/hash-types/build/tools/abidw -d usr/lib/debug
usr/lib64/libgs.so.9.27 > libgs.so.9.27.hashed.abi
real 0m45,004s
user 0m44,734s
sys 0m0,142s
$
In other words, the current type-hashing work on the branch
https://sourceware.org/git/?p=libabigail.git;a=shortlog;h=refs/heads/users/dodji/hash-types
seems to address precisely this kind of issues.
I'll look into this a bit more to see if I can find a work-around before I am
done with the type-hashing work. But we might as well wait for type-hashing
work to land.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2024-02-14 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 18:47 [Bug default/31313] New: " fche at redhat dot com
2024-01-29 18:48 ` [Bug default/31313] " fche at redhat dot com
2024-02-14 13:51 ` dodji at redhat dot com [this message]
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-31313-9487-GSqr4W5QM4@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).