From: Arseniy Aharonov <aaharonov@nvidia.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Multi-versioning for backward compatibility
Date: Wed, 1 Feb 2023 14:54:03 +0000 [thread overview]
Message-ID: <MW4PR12MB5666792D438D8C0CDC0FA343CBD19@MW4PR12MB5666.namprd12.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
Hi,
In the codebase of DPDK I saw that it uses the glibc approach<https://developers.redhat.com/blog/2019/08/01/how-the-gnu-c-library-handles-backward-compatibility> to mangle symbol names with a library version to maintain different implementations of the same function per version.
So that applications which were compiled with different versions of the library will link to a proper version of the function that corresponds to the right glibc (see doc<https://doc.dpdk.org/guides/contributing/abi_versioning.html>).
This method can't work in Windows with MSVC (at least to the best of my knowledge).
How does DPDK solve if in Windows for MSVC? I failed to find the answer.
Thank you,
Arseniy Aharonov
[-- Attachment #2: Type: text/html, Size: 2849 bytes --]
next reply other threads:[~2023-02-01 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 14:54 Arseniy Aharonov [this message]
2023-02-01 15:33 ` Dmitry Kozlyuk
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=MW4PR12MB5666792D438D8C0CDC0FA343CBD19@MW4PR12MB5666.namprd12.prod.outlook.com \
--to=aaharonov@nvidia.com \
--cc=dev@dpdk.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 NNTP newsgroup(s).