From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30034] [libabigail] Handle library splitting
Date: Mon, 26 Jun 2023 10:11:15 +0000 [thread overview]
Message-ID: <bug-30034-9487-lOCNUu6XKK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30034-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30034
--- Comment #19 from dodji at redhat dot com ---
(In reply to David Marchand from comment #17)
> Once I disable CTF support, it can compile fine.
>
> So I ran DPDK full ABI check:
>
> Before (w/o follow dependencies):
> real 0m2,951s
> user 0m22,876s
> sys 0m3,724s
>
> After (with follow dependencies):
> real 0m21,659s
> user 3m4,138s
> sys 1m52,617s
>
> I did not look too much into it yet, but it seems significantly heavier.
Hmmh, I am wondering if you have *all* the dependencies of the library,
including all system libraries and everything (like libc etc) in the
dependencies directory specified by --deps-dir{1,2}. If so, then it's normal
that things are much heavier.
To know what dependencies are taken into account account by abidiff, I have
just added a --list-dependencies option to abidiff in the branch. Could you
please provide me with the list of deps so that we have an idea?
Here is how the --list-dependencies option can be used:
$ time /home/dodji/git/libabigail/PR30034/build/tools/abidiff
--follow-dependencies --list-dependencies --suppr libabigail.abignore
--no-added-syms --headers-dir1 reference/include --headers-dir2 split/include
--deps-dir1 reference/lib64 --deps-dir2 split/lib64
reference/lib64/librte_eal.so split/lib64/librte_eal.so
Functions changes summary: 0 Removed, 0 Changed (1 filtered out), 0
Added (12 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
/home/dodji/git/libabigail/PR30034/build/tools/.libs/lt-abidiff:
dependencies of 'reference/lib64/librte_eal.so':
reference/lib64/librte_kvargs.so.23,
reference/lib64/librte_telemetry.so.23
/home/dodji/git/libabigail/PR30034/build/tools/.libs/lt-abidiff:
dependencies of 'split/lib64/librte_eal.so':
split/lib64/librte_kvargs.so.23, split/lib64/librte_log.so.23,
split/lib64/librte_telemetry.so.23
real 0m0,662s
user 0m0,638s
sys 0m0,026s
$
Thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-06-26 10:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 13:45 [Bug default/30034] New: " david.marchand at redhat dot com
2023-06-02 17:53 ` [Bug default/30034] " dodji at redhat dot com
2023-06-05 8:04 ` david.marchand at redhat dot com
2023-06-05 11:01 ` dodji at redhat dot com
2023-06-05 15:08 ` david.marchand at redhat dot com
2023-06-05 15:24 ` woodard at redhat dot com
2023-06-05 15:36 ` dodji at redhat dot com
2023-06-05 16:53 ` woodard at redhat dot com
2023-06-06 7:28 ` david.marchand at redhat dot com
2023-06-06 21:07 ` woodard at redhat dot com
2023-06-09 12:29 ` dodji at redhat dot com
2023-06-14 12:22 ` david.marchand at redhat dot com
2023-06-23 8:30 ` david.marchand at redhat dot com
2023-06-23 8:32 ` david.marchand at redhat dot com
2023-06-23 10:17 ` david.marchand at redhat dot com
2023-06-24 14:19 ` dodji at redhat dot com
2023-06-24 14:32 ` dodji at redhat dot com
2023-06-25 8:17 ` david.marchand at redhat dot com
2023-06-25 8:37 ` david.marchand at redhat dot com
2023-06-26 10:07 ` dodji at redhat dot com
2023-06-26 10:11 ` dodji at redhat dot com [this message]
2023-06-26 12:13 ` david.marchand at redhat dot com
2023-06-26 12:41 ` david.marchand at redhat dot com
2023-06-26 13:57 ` dodji at redhat dot com
2023-07-06 13:38 ` david.marchand at redhat dot com
2023-07-07 8:38 ` Dodji Seketeli
2023-07-07 8:39 ` dodji at seketeli dot org
2023-07-07 11:48 ` dodji at redhat dot com
2023-07-07 13:55 ` fweimer at redhat dot com
2023-07-07 18:18 ` 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-30034-9487-lOCNUu6XKK@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).