DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>,
	Andre Muezerie <andremue@linux.microsoft.com>
Cc: dev@dpdk.org, Ori Kam <orika@nvidia.com>
Subject: Re: [PATCH] regexdev: enable to be compiled on Windows
Date: Fri, 16 May 2025 16:44:38 +0200	[thread overview]
Message-ID: <8651425.NyiUUSuA9g@thomas> (raw)
In-Reply-To: <20250516125035.GA29027@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>

16/05/2025 14:50, Andre Muezerie:
> On Fri, May 16, 2025 at 10:01:42AM +0200, David Marchand wrote:
> > On Fri, May 9, 2025 at 11:52 PM Andre Muezerie
> > <andremue@linux.microsoft.com> wrote:
> > >
> > > Now that mbuf is compiling on Windows, this library can be enabled as
> > > well.
> > >
> > > Signed-off-by: Andre Muezerie <andremue@linux.microsoft.com>
> > 
> > The test-regex app can probably be compiled too.
> > Yet.. why do you want to enable this library on Windows?
> > 
> > Support for this device class is defacto deprecated, as no vendor is
> > providing recent hardware implementing this feature.
> > 
> > Also note that it was not built with clang on Windows so far (I did
> > not double check this assertion, I just based on the fact this patch
> > removes a is_windows, and not a is_ms_compiler).
> > 
> > 
> 
> I was not aware this code was deprecated. You're right that it was not
> being compiled with Clang. This was just part of the effort to increase
> code compatibility on Windows.
> 
> I see no harm in enabling it, but at the same time, there's no clear
> benefit either. I'll let you decide what to do with this.

The benefit is to remove special handling for Windows,
so I vote for enabling it.
There was no regex development recently but we never know
how it could be used in future :)



      reply	other threads:[~2025-05-16 14:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-09 21:52 Andre Muezerie
2025-05-16  8:01 ` David Marchand
2025-05-16 12:50   ` Andre Muezerie
2025-05-16 14:44     ` Thomas Monjalon [this message]

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=8651425.NyiUUSuA9g@thomas \
    --to=thomas@monjalon.net \
    --cc=andremue@linux.microsoft.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=orika@nvidia.com \
    /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).