From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/19355] [PERF] Libabigail slow on the r300_dri.so binary
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <bug-19355-9487-1KWDZd9eRX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19355-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19355
dodji at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #1 from dodji at redhat dot com ---
Let's provide more numbers and perspective to this one.
abidw --abidiff r300_dri.so, on a version of r300_dri.so that has been dwz'ed
is even slower. On my system, it's taking ~ 53 minutes and it's aborting!!!
So the priority now is to reduce the time taken on the dwz'ed version.
Profiling showed that most of the time is taken during what we could call the
"decompressing phase". Basically, getting the logical parent of a debug
information entry (aka DIE) that has been imported (using the
DW_TAG_imported_unit kind of DIE) is what's taking the most time.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-01-04 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 [Bug default/19355] New: " dodji at redhat dot com
2016-01-01 0:00 ` [Bug default/19355] " dodji at redhat dot com
2016-01-01 0:00 ` dodji at redhat dot com [this message]
2016-01-01 0:00 ` dodji at redhat dot com
2016-01-01 0:00 ` dodji at redhat dot com
2016-01-01 0:00 ` dodji at redhat dot com
2016-01-01 0:00 ` dodji at redhat dot com
2020-11-11 16:55 ` maennich at android 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-19355-9487-1KWDZd9eRX@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).