From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 848] gcc12 build error, app/test
Date: Thu, 28 Oct 2021 12:01:05 +0000 [thread overview]
Message-ID: <bug-848-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=848
Bug ID: 848
Summary: gcc12 build error, app/test
Product: DPDK
Version: 20.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: ferruh.yigit@intel.com
Target Milestone: ---
With gcc 12.0.0 "gcc (GCC) 12.0.0 20211024 (experimental)"
In file included from
/usr/local/gcc-latest/lib/gcc/x86_64-pc-linux-gnu/12.0.0/include/immintrin.h:43,
from
/usr/local/gcc-latest/lib/gcc/x86_64-pc-linux-gnu/12.0.0/include/x86intrin.h:32,
from ../lib/eal/x86/include/rte_vect.h:31,
from ../lib/eal/x86/include/rte_memcpy.h:17,
from ../lib/mempool/rte_mempool.h:50,
from ../lib/mbuf/rte_mbuf.h:38,
from ../app/test/test_ipsec.c:9:
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/x86/include/rte_memcpy.h:438:4,
inlined from ‘rte_memcpy’ at ../lib/eal/x86/include/rte_memcpy.h:882:10,
inlined from ‘setup_test_string.constprop’ at
../app/test/test_ipsec.c:561:4:
/usr/local/gcc-latest/lib/gcc/x86_64-pc-linux-gnu/12.0.0/include/avxintrin.h:929:10:
warning: array subscript ‘__m256i_u[3]’ is partly outside array bounds of
‘const char[108]’ [-Warray-bounds]
929 | return *__P;
| ^~~~
../app/test/test_ipsec.c: In function ‘setup_test_string.constprop’:
../app/test/test_ipsec.c:528:12: note: at offset 96 into object
‘null_plain_data’ of size 108
528 | const char null_plain_data[] =
| ^~~~~~~~~~~~~~~
In file included from
/usr/local/gcc-latest/lib/gcc/x86_64-pc-linux-gnu/12.0.0/include/immintrin.h:43,
from
/usr/local/gcc-latest/lib/gcc/x86_64-pc-linux-gnu/12.0.0/include/x86intrin.h:32,
from ../lib/eal/x86/include/rte_vect.h:31,
from ../lib/eal/x86/include/rte_memcpy.h:17,
from ../lib/mempool/rte_mempool.h:50,
from ../lib/mbuf/rte_mbuf.h:38,
from ../app/test/test_ipsec.c:9:
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/x86/include/rte_memcpy.h:438:4,
inlined from ‘rte_memcpy’ at ../lib/eal/x86/include/rte_memcpy.h:882:10,
inlined from ‘setup_test_string’ at ../app/test/test_ipsec.c:561:4,
inlined from ‘test_ipsec_lksd_proto_inb_burst_null_null’ at
../app/test/test_ipsec.c:1806:24:
/usr/local/gcc-latest/lib/gcc/x86_64-pc-linux-gnu/12.0.0/include/avxintrin.h:929:10:
warning: array subscript ‘__m256i_u[3]’ is partly outside array bounds of
‘const char[108]’ [-Warray-bounds]
929 | return *__P;
| ^~~~
../app/test/test_ipsec.c: In function
‘test_ipsec_lksd_proto_inb_burst_null_null’:
../app/test/test_ipsec.c:532:12: note: at offset 96 into object
‘null_encrypted_data’ of size 108
532 | const char null_encrypted_data[] =
| ^~~~~~~~~~~~~~~~~~~
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-10-28 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 12:01 bugzilla [this message]
2022-06-24 8:27 ` [Bug 848] gcc12 build error, app/test bugzilla
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=bug-848-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.