Re: [dpdk-dev] [PATCH v2] eal: fix rte_memcpy build on ppc with gcc 9.3

2020-05-06 Thread David Marchand
On Mon, May 4, 2020 at 11:04 PM David Christensen wrote: > > Building DPDK on Ubuntu 20.04 with GCC 9.3.0 results in a "subscript is > outside array bounds" message in rte_memcpy function. The build error > is caused by an interaction between __builtin_constant_p and > "-Werror=array-bounds" as d

Re: [dpdk-dev] [PATCH v2] eal: fix rte_memcpy build on ppc with gcc 9.3

2020-05-06 Thread David Christensen
Though it is probably worth backporting if it is a problem with gcc 9.x. WDYT? I can add a Cc: sta...@dpdk.org when applying. Agree, should be backported. Dave

Re: [dpdk-dev] [PATCH v2] eal: fix rte_memcpy build on ppc with gcc 9.3

2020-05-06 Thread David Marchand
On Tue, May 5, 2020 at 10:28 PM David Christensen wrote: > > > >> The rte_altivec.h is related to another open patch required to build on > >> POWER systems (http://patches.dpdk.org/patch/69605/) that's waiting to > >> be accepted. You may not have encountered it if you're not building the > >> M

Re: [dpdk-dev] [PATCH v2] eal: fix rte_memcpy build on ppc with gcc 9.3

2020-05-06 Thread Ferruh Yigit
On 5/5/2020 9:37 PM, David Christensen wrote: I can't find "rte_altivec.h", am I missing something. With just ignoring "-Warray-bounds" changes, I confirm ena build issue is fixed with gcc 9.1 >>> >>> The rte_altivec.h is related to another open patch required to build on

Re: [dpdk-dev] [PATCH v2] eal: fix rte_memcpy build on ppc with gcc 9.3

2020-05-05 Thread David Christensen
I can't find "rte_altivec.h", am I missing something. With just ignoring "-Warray-bounds" changes, I confirm ena build issue is fixed with gcc 9.1 The rte_altivec.h is related to another open patch required to build on POWER systems (http://patches.dpdk.org/patch/69605/) that's waiting to be ac

Re: [dpdk-dev] [PATCH v2] eal: fix rte_memcpy build on ppc with gcc 9.3

2020-05-05 Thread David Christensen
The rte_altivec.h is related to another open patch required to build on POWER systems (http://patches.dpdk.org/patch/69605/) that's waiting to be accepted. You may not have encountered it if you're not building the MLX5 PMD which has additional library requirements. Is there a point in havin

Re: [dpdk-dev] [PATCH v2] eal: fix rte_memcpy build on ppc with gcc 9.3

2020-05-05 Thread Ferruh Yigit
On 5/5/2020 5:32 PM, David Christensen wrote: > > >>> diff --git a/lib/librte_eal/ppc/include/rte_memcpy.h >>> b/lib/librte_eal/ppc/include/rte_memcpy.h >>> index 25311ba1d..de47a5d2e 100644 >>> --- a/lib/librte_eal/ppc/include/rte_memcpy.h >>> +++ b/lib/librte_eal/ppc/include/rte_memcpy.h >>> @

Re: [dpdk-dev] [PATCH v2] eal: fix rte_memcpy build on ppc with gcc 9.3

2020-05-05 Thread David Marchand
On Tue, May 5, 2020 at 6:32 PM David Christensen wrote: > >> diff --git a/lib/librte_eal/ppc/include/rte_memcpy.h > >> b/lib/librte_eal/ppc/include/rte_memcpy.h > >> index 25311ba1d..de47a5d2e 100644 > >> --- a/lib/librte_eal/ppc/include/rte_memcpy.h > >> +++ b/lib/librte_eal/ppc/include/rte_mem

Re: [dpdk-dev] [PATCH v2] eal: fix rte_memcpy build on ppc with gcc 9.3

2020-05-05 Thread David Christensen
diff --git a/lib/librte_eal/ppc/include/rte_memcpy.h b/lib/librte_eal/ppc/include/rte_memcpy.h index 25311ba1d..de47a5d2e 100644 --- a/lib/librte_eal/ppc/include/rte_memcpy.h +++ b/lib/librte_eal/ppc/include/rte_memcpy.h @@ -8,8 +8,8 @@ #include #include -/*To include altivec.h, GCC

Re: [dpdk-dev] [PATCH v2] eal: fix rte_memcpy build on ppc with gcc 9.3

2020-05-05 Thread Ferruh Yigit
On 5/4/2020 10:03 PM, David Christensen wrote: > Building DPDK on Ubuntu 20.04 with GCC 9.3.0 results in a "subscript is > outside array bounds" message in rte_memcpy function. The build error > is caused by an interaction between __builtin_constant_p and > "-Werror=array-bounds" as described in t

[dpdk-dev] [PATCH v2] eal: fix rte_memcpy build on ppc with gcc 9.3

2020-05-04 Thread David Christensen
Building DPDK on Ubuntu 20.04 with GCC 9.3.0 results in a "subscript is outside array bounds" message in rte_memcpy function. The build error is caused by an interaction between __builtin_constant_p and "-Werror=array-bounds" as described in this bugzilla: https://gcc.gnu.org/bugzilla/show_bug.cg