From: Amit Prakash Shukla <amitprakashs@marvell.com>
To: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
Bernard Iremonger <bernard.iremonger@intel.com>,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Cc: <dev@dpdk.org>, <jerinj@marvell.com>,
Amit Prakash Shukla <amitprakashs@marvell.com>
Subject: [PATCH 1/3] test/test_ipsec: compilation fix for GCC-12
Date: Thu, 4 Aug 2022 19:10:53 +0530 [thread overview]
Message-ID: <20220804134055.1816993-1-amitprakashs@marvell.com> (raw)
GCC-12 raises following warning:
p/test/dpdk-test.p/test_ipsec.c.o -c ../app/test/test_ipsec.c
In file included from ../lib/eal/x86/include/rte_atomic.h:15,
from ../lib/eal/include/generic/rte_pause.h:19,
from ../lib/eal/x86/include/rte_pause.h:12,
from ../lib/eal/include/generic/rte_spinlock.h:25,
from ../lib/eal/x86/include/rte_spinlock.h:12,
from ../lib/mempool/rte_mempool.h:43,
from ../lib/mbuf/rte_mbuf.h:38,
from ../app/test/test_ipsec.c:9:
In function '_mm_loadu_si128',
inlined from 'rte_mov16' at
../lib/eal/x86/include/rte_memcpy.h:507:9,
inlined from 'rte_mov128' at
../lib/eal/x86/include/rte_memcpy.h:549:2,
inlined from 'rte_memcpy_generic' at
../lib/eal/x86/include/rte_memcpy.h:732:4,
inlined from 'rte_memcpy' at
../lib/eal/x86/include/rte_memcpy.h:882:10,
inlined from 'setup_test_string_tunneled' at
../app/test/test_ipsec.c:617:3:
/usr/lib/gcc/x86_64-pc-linux-gnu/12.1.1/include/emmintrin.h:703:10: error:
array subscript '__m128i_u[15]' is partly outside array bounds of
'const uint8_t[255]' {aka 'const unsigned char[255]'}
[-Werror=array-bounds]
703 | return *__P;
| ^~~~
../app/test/test_ipsec.c: In function 'setup_test_string_tunneled':
../app/test/test_ipsec.c:491:22: note: at offset 240 into object
'esp_pad_bytes' of size 255
491 | static const uint8_t esp_pad_bytes[IPSEC_MAX_PAD_SIZE] = {
Restrict copy to minimum size.
Signed-off-by: Amit Prakash Shukla <amitprakashs@marvell.com>
---
app/test/test_ipsec.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/app/test/test_ipsec.c b/app/test/test_ipsec.c
index bc2a3dbc2e..8fad093dee 100644
--- a/app/test/test_ipsec.c
+++ b/app/test/test_ipsec.c
@@ -614,7 +614,8 @@ setup_test_string_tunneled(struct rte_mempool *mpool, const char *string,
rte_memcpy(dst, string, len);
dst += len;
/* copy pad bytes */
- rte_memcpy(dst, esp_pad_bytes, padlen);
+ rte_memcpy(dst, esp_pad_bytes, RTE_MIN(padlen,
+ sizeof(esp_pad_bytes)));
dst += padlen;
/* copy ESP tail header */
rte_memcpy(dst, &espt, sizeof(espt));
--
2.25.1
next reply other threads:[~2022-08-04 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 13:40 Amit Prakash Shukla [this message]
2022-08-04 13:40 ` [PATCH 2/3] ipsec: " Amit Prakash Shukla
2022-08-07 13:17 ` Konstantin Ananyev
2022-08-04 13:40 ` [PATCH 3/3] crypto/qat: " Amit Prakash Shukla
2022-08-05 8:12 ` Zhang, Roy Fan
2022-08-28 12:01 ` [EXT] [PATCH 1/3] test/test_ipsec: " Akhil Goyal
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=20220804134055.1816993-1-amitprakashs@marvell.com \
--to=amitprakashs@marvell.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=vladimir.medvedkin@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).