[dpdk-dev] [PATCH v3 0/2] fix mingw build error

Rong, Leyi leyi.rong at intel.com
Tue Feb 2 10:09:36 CET 2021


> -----Original Message-----
> From: David Marchand <david.marchand at redhat.com>
> Sent: Tuesday, February 2, 2021 4:37 PM
> To: Rong, Leyi <leyi.rong at intel.com>; Dmitry Kozlyuk
> <dmitry.kozliuk at gmail.com>
> Cc: Thomas Monjalon <thomas at monjalon.net>; Richardson, Bruce
> <bruce.richardson at intel.com>; Tal Shnaiderman <talshn at nvidia.com>; Zhang,
> Qi Z <qi.z.zhang at intel.com>; Kadam, Pallavi <pallavi.kadam at intel.com>; Yigit,
> Ferruh <ferruh.yigit at intel.com>; Menon, Ranjit <ranjit.menon at intel.com>; Xing,
> Beilei <beilei.xing at intel.com>; dev <dev at dpdk.org>; Aaron Conole
> <aconole at redhat.com>; ci at dpdk.org; dpdklab <dpdklab at iol.unh.edu>
> Subject: Re: [dpdk-dev] [PATCH v3 0/2] fix mingw build error
> 
> On Thu, Jan 28, 2021 at 10:27 PM Thomas Monjalon <thomas at monjalon.net>
> wrote:
> >
> > 28/01/2021 13:28, David Marchand:
> > > On Wed, Jan 27, 2021 at 3:47 PM Leyi Rong <leyi.rong at intel.com> wrote:
> > > >
> > > > This patchset fix mingw build error when avx512 is introduced.
> > > >
> > > > ---
> > > > v2:
> > > > - Set i40e_avx512_cc_support to false to avoid the build error under
> > > >   windows with mingw.
> > > >
> > > > Leyi Rong (2):
> > > >   config: disable avx512 on mingw cross build
> > > >   net/i40e: fix mingw build error
> > > >
> > > >  config/x86/cross-mingw       | 3 +++
> > > >  drivers/net/i40e/meson.build | 4 ++++
> > > >  2 files changed, 7 insertions(+)
> > >
> > > LGTM with fc32 mingw.
> > > Tested-by: David Marchand <david.marchand at redhat.com>
> >
> > Applied, thanks.
> >
> > Dmitry found a lighter alternative option to be tested and discussed.
> 
> We still have build failures at UNH for Windows, on the rc2 tag:
> http://mails.dpdk.org/archives/test-report/2021-February/177464.html
> 
> Is this issue being looked at?
> 
> 
> --
> David Marchand

Hi David,

Seems the issue still exist on the platform which CPU has AVX512 capability, I think previous patch is not verified to cover this case.
Will send hotfix patch for this.


More information about the dev mailing list