DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andre Muezerie <andremue@linux.microsoft.com>
To: andremue@linux.microsoft.com
Cc: dev@dpdk.org
Subject: [PATCH v4 0/1] mbuf: enable to be compiled with MSVC
Date: Tue,  8 Apr 2025 14:24:36 -0700	[thread overview]
Message-ID: <1744147477-23715-1-git-send-email-andremue@linux.microsoft.com> (raw)
In-Reply-To: <1739224265-4158-1-git-send-email-andremue@linux.microsoft.com>

Now that the issues preventing this lib from being compiled with MSVC
are fixed it can be included in the compilation.

v4:
- removed all symbol-related changes, leaving only the change to enable
  MSVC compilation.
- only adding cflags '-mpclmul' and '-maes' when the compiler used
  supports them.

v3:
- updated check-symbol-maps.sh to also handle ms_linker.map files.

v2:
- updated versioning macros so that the latest mbuf/net code can compile
  with MSVC. V1 did not have these changes because by the time that series
  was sent out the versioning problem had not surfaced yet.
- for testing purposes, dpdk-test was build with msvc and crc_autotest
  was run successfully. This test is known to call the versioned function
  which raised the issue.

Andre Muezerie (1):
  mbuf: enable to be compiled with MSVC

 lib/mbuf/meson.build | 6 ------
 lib/net/meson.build  | 7 ++++++-
 2 files changed, 6 insertions(+), 7 deletions(-)

--
2.49.0.vfs.0.0


  parent reply	other threads:[~2025-04-08 21:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 21:51 [PATCH] " 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   ` [PATCH v2 1/5] doc: update guide on versioning macros Andre Muezerie
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 ` Andre Muezerie [this message]
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=1744147477-23715-1-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 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).