On Wed, 18 May 2022 12:16:57 +0200
David Marchand wrote:
> GCC 12 raises the following warning:
>
> In function ‘_mm256_loadu_si256’,
> inlined from ‘rte_mov32’ at
> ../lib/eal/x86/include/rte_memcpy.h:319:9,
> inlined from ‘rte_mov128’ at
> ../lib/eal/x86/include/rte_mem
Hi David,
On 03/06/2022 10:41, David Marchand wrote:
On Fri, Jun 3, 2022 at 9:56 AM Bruce Richardson
wrote:
On Fri, Jun 03, 2022 at 09:45:45AM +0200, David Marchand wrote:
Hello Vladimir,
On Thu, Jun 2, 2022 at 8:42 PM Medvedkin, Vladimir
wrote:
if (!dst) {
On Fri, Jun 3, 2022 at 9:56 AM Bruce Richardson
wrote:
>
> On Fri, Jun 03, 2022 at 09:45:45AM +0200, David Marchand wrote:
> > Hello Vladimir,
> >
> > On Thu, Jun 2, 2022 at 8:42 PM Medvedkin, Vladimir
> > wrote:
> > > > if (!dst) {
> > > > rte_pktmbuf_free(m);
On Fri, Jun 03, 2022 at 09:45:45AM +0200, David Marchand wrote:
> Hello Vladimir,
>
> On Thu, Jun 2, 2022 at 8:42 PM Medvedkin, Vladimir
> wrote:
> > > if (!dst) {
> > > rte_pktmbuf_free(m);
> > > return NULL;
> > > }
> > > -
Hello Vladimir,
On Thu, Jun 2, 2022 at 8:42 PM Medvedkin, Vladimir
wrote:
> > if (!dst) {
> > rte_pktmbuf_free(m);
> > return NULL;
> > }
> > - if (string != NULL)
> > - rte_memcpy(dst, string,
Hi David,
On 18/05/2022 11:16, David Marchand wrote:
GCC 12 raises the following warning:
In function ‘_mm256_loadu_si256’,
inlined from ‘rte_mov32’ at
../lib/eal/x86/include/rte_memcpy.h:319:9,
inlined from ‘rte_mov128’ at
../lib/eal/x86/include/rte_memcpy.h:344:2,
GCC 12 raises the following warning:
In function ‘_mm256_loadu_si256’,
inlined from ‘rte_mov32’ at
../lib/eal/x86/include/rte_memcpy.h:319:9,
inlined from ‘rte_mov128’ at
../lib/eal/x86/include/rte_memcpy.h:344:2,
inlined from ‘rte_memcpy_generic’ at
../lib/eal/
7 matches
Mail list logo