All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Muezerie <andremue@linux.microsoft.com>
To: andremue@linux.microsoft.com
Cc: dev@dpdk.org
Subject: [PATCH v2 1/5] doc: update guide on versioning macros
Date: Tue, 18 Feb 2025 17:39:54 -0800	[thread overview]
Message-ID: <1739929198-28432-2-git-send-email-andremue@linux.microsoft.com> (raw)
In-Reply-To: <1739929198-28432-1-git-send-email-andremue@linux.microsoft.com>

Added explanation about new macro MAP_STATIC_BASE_SYMBOL.

Signed-off-by: Andre Muezerie <andremue@linux.microsoft.com>
---
 doc/guides/contributing/abi_versioning.rst | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/guides/contributing/abi_versioning.rst b/doc/guides/contributing/abi_versioning.rst
index 7afd1c1886..1179445da3 100644
--- a/doc/guides/contributing/abi_versioning.rst
+++ b/doc/guides/contributing/abi_versioning.rst
@@ -151,6 +151,11 @@ The macros exported are:
   fully qualified function ``p``, so that if a symbol becomes versioned, it
   can still be mapped back to the public symbol name.
 
+* ``MAP_STATIC_BASE_SYMBOL(b, p)``: Declare the base symbol ``b``, and map it
+  to the fully qualified function ``p``, so that if a symbol becomes versioned,
+  it can still be mapped back to the public symbol name. Used for compatibility
+  with MSVC.
+
 * ``__vsym``:  Annotation to be used in a declaration of the internal symbol
   ``be`` to signal that it is being used as an implementation of a particular
   version of symbol ``b``.
@@ -397,6 +402,7 @@ defined, we add this
         ...
    }
    MAP_STATIC_SYMBOL(struct rte_acl_ctx *rte_acl_create(const struct rte_acl_param *param, int debug), rte_acl_create_v22);
+   MAP_STATIC_BASE_SYMBOL(rte_acl_create, rte_acl_create_v22);
 
 That tells the compiler that, when building a static library, any calls to the
 symbol ``rte_acl_create`` should be linked to ``rte_acl_create_v22``
-- 
2.48.1.vfs.0.0


  reply	other threads:[~2025-02-19  1:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 21:51 [PATCH] mbuf: enable to be compiled with MSVC Andre Muezerie
2025-02-10 22:34 ` Stephen Hemminger
2025-02-11  2:19   ` Andre Muezerie
2025-02-12 14:23     ` Thomas Monjalon
2025-02-12 16:24       ` Thomas Monjalon
2025-02-19  1:39 ` [PATCH v2 0/5] " Andre Muezerie
2025-02-19  1:39   ` Andre Muezerie [this message]
2025-02-19  1:39   ` [PATCH v2 2/5] buildtools: update map_to_win.py to use optional map file Andre Muezerie
2025-02-19  1:39   ` [PATCH v2 3/5] eal: update versioning macros Andre Muezerie
2025-03-06 12:59     ` David Marchand
2025-03-06 15:53       ` Andre Muezerie
2025-02-19  1:39   ` [PATCH v2 4/5] net: update use of " Andre Muezerie
2025-02-19  1:39   ` [PATCH v2 5/5] mbuf: enable to be compiled with MSVC Andre Muezerie
2025-02-20 20:31 ` [PATCH v3 0/6] " Andre Muezerie
2025-02-20 20:31   ` [PATCH v3 1/6] doc: update guide on versioning macros Andre Muezerie
2025-02-20 20:31   ` [PATCH v3 2/6] buildtools: update map_to_win.py to use optional map file Andre Muezerie
2025-02-20 20:31   ` [PATCH v3 3/6] eal: update versioning macros Andre Muezerie
2025-02-20 20:31   ` [PATCH v3 4/6] devtools: check ms linker map files Andre Muezerie
2025-02-20 20:31   ` [PATCH v3 5/6] net: update use of versioning macros Andre Muezerie
2025-02-20 20:31   ` [PATCH v3 6/6] mbuf: enable to be compiled with MSVC Andre Muezerie
2025-04-07 13:53     ` David Marchand
2025-04-08 20:53       ` Andre Muezerie
2025-04-08 21:24 ` [PATCH v4 0/1] " Andre Muezerie
2025-04-08 21:24   ` [PATCH v4 1/1] " Andre Muezerie
2025-04-09 11:39     ` David Marchand
2025-04-09 13:42       ` Andre Muezerie
2025-04-12  0:46         ` Andre Muezerie
2025-04-10  9:45     ` David Marchand

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=1739929198-28432-2-git-send-email-andremue@linux.microsoft.com \
    --to=andremue@linux.microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.