DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v4 1/1] mbuf: enable to be compiled with MSVC
Date: Wed, 9 Apr 2025 13:39:36 +0200	[thread overview]
Message-ID: <CAJFAV8xCqwbMEsf83Um-m=Kn1n=SU9k1bpB2jtuhjPFDQiJs3w@mail.gmail.com> (raw)
In-Reply-To: <1744147477-23715-2-git-send-email-andremue@linux.microsoft.com>

On Tue, Apr 8, 2025 at 11:24 PM Andre Muezerie
<andremue@linux.microsoft.com> wrote:
> diff --git a/lib/net/meson.build b/lib/net/meson.build
> index 7a6c419f40..c528fcc9a2 100644
> --- a/lib/net/meson.build
> +++ b/lib/net/meson.build
> @@ -43,7 +43,12 @@ use_function_versioning = true
>
>  if dpdk_conf.has('RTE_ARCH_X86_64')
>      sources += files('net_crc_sse.c')
> -    cflags += ['-mpclmul', '-maes']
> +    cflags_options = ['-mpclmul', '-maes']
> +    foreach option:cflags_options
> +        if cc.has_argument(option)
> +            cflags += option
> +        endif
> +    endforeach

What guarantee do we have that MSVC builds with those instructions?

>      # only build AVX-512 support if we also have PCLMULQDQ support
>      if cc.has_argument('-mvpclmulqdq')
>          sources_avx512 += files('net_crc_avx512.c')


-- 
David Marchand


  reply	other threads:[~2025-04-09 11:39 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 ` [PATCH v4 0/1] " Andre Muezerie
2025-04-08 21:24   ` [PATCH v4 1/1] " Andre Muezerie
2025-04-09 11:39     ` David Marchand [this message]
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='CAJFAV8xCqwbMEsf83Um-m=Kn1n=SU9k1bpB2jtuhjPFDQiJs3w@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=andremue@linux.microsoft.com \
    --cc=bruce.richardson@intel.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).