[dpdk-dev] [PATCH 4/4] devtools: add Windows cross-build test with MinGW
Thomas Monjalon
thomas at monjalon.net
Mon Jun 15 09:51:48 CEST 2020
15/06/2020 03:05, Dmitry Kozlyuk:
> > It looks to be a false positive, but we need to find a way to remove
> > the warning with a code change.
> >
> > This workaround in lib/librte_eal/common/eal_common_options.c
> > makes 200% sure the default_set is initialized:
> >
> > - if (pthread_getaffinity_np(pthread_self(), sizeof(rte_cpuset_t),
> > - &default_set))
> > - CPU_ZERO(&default_set);
> > -
> > + CPU_ZERO(&default_set);
> > + pthread_getaffinity_np(pthread_self(),
> > + sizeof default_set, &default_set);
> >
>
> Doesn't look like a false-positive to me. That's where it's been spotted
> and explained before:
>
> https://mails.dpdk.org/archives/dev/2020-May/168634.html
>
> And this series eliminates it along with other improvements:
>
> http://patchwork.dpdk.org/patch/70727/
I see.
So the fix must be explained (and probably a separate patch).
More information about the dev
mailing list