From: "david.marchand at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30034] [libabigail] Handle library splitting
Date: Fri, 23 Jun 2023 08:30:57 +0000 [thread overview]
Message-ID: <bug-30034-9487-nvXmtZOXqq@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 #12 from David Marchand <david.marchand at redhat dot com> ---
To give an example on the split we are currently planning to go with:
https://patchwork.dpdk.org/project/dpdk/list/?series=28061&state=%2A&archive=both
I will attach the (reference and new) binaries to this bz.
The command we use to compare atm:
$ abidiff --suppr libabigail.abignore --no-added-syms --headers-dir1
reference/include --headers-dir2 split/include
reference/lib64/librte_eal.so.23.1 split/lib64/librte_eal.so.23.2
Functions changes summary: 17 Removed, 0 Changed, 0 Added (6 filtered out)
functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
17 Removed functions:
[D] 'function int rte_log(uint32_t, uint32_t, const char*, ...)'
{rte_log@@DPDK_23}
[D] 'function bool rte_log_can_log(uint32_t, uint32_t)'
{rte_log_can_log@@DPDK_23}
[D] 'function int rte_log_cur_msg_loglevel()'
{rte_log_cur_msg_loglevel@@DPDK_23}
[D] 'function int rte_log_cur_msg_logtype()'
{rte_log_cur_msg_logtype@@DPDK_23}
[D] 'function void rte_log_dump(FILE*)' {rte_log_dump@@DPDK_23}
[D] 'function uint32_t rte_log_get_global_level()'
{rte_log_get_global_level@@DPDK_23}
[D] 'function int rte_log_get_level(uint32_t)'
{rte_log_get_level@@DPDK_23}
[D] 'function FILE* rte_log_get_stream()' {rte_log_get_stream@@DPDK_23}
[D] 'function void rte_log_list_types(FILE*, const char*)'
{rte_log_list_types@@DPDK_23}
[D] 'function int rte_log_register(const char*)'
{rte_log_register@@DPDK_23}
[D] 'function int rte_log_register_type_and_pick_level(const char*,
uint32_t)' {rte_log_register_type_and_pick_level@@DPDK_23}
[D] 'function void rte_log_set_global_level(uint32_t)'
{rte_log_set_global_level@@DPDK_23}
[D] 'function int rte_log_set_level(uint32_t, uint32_t)'
{rte_log_set_level@@DPDK_23}
[D] 'function int rte_log_set_level_pattern(const char*, uint32_t)'
{rte_log_set_level_pattern@@DPDK_23}
[D] 'function int rte_log_set_level_regexp(const char*, uint32_t)'
{rte_log_set_level_regexp@@DPDK_23}
[D] 'function int rte_openlog_stream(FILE*)' {rte_openlog_stream@@DPDK_23}
[D] 'function int rte_vlog(uint32_t, uint32_t, const char*, __va_list_tag*)'
{rte_vlog@@DPDK_23}
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-06-23 8:31 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 [this message]
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
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-nvXmtZOXqq@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).