Hi David,
>-----Original Message-----
>From: David Marchand <david.march...@redhat.com>
>Sent: Friday, June 10, 2022 6:42 PM
>To: Anoob Joseph <ano...@marvell.com>; Ankur Dwivedi
><adwiv...@marvell.com>
>Cc: Thomas Monjalon <tho...@monjalon.net>; Ferruh Yigit
><ferruh.yi...@xilinx.com>; dpdk stable <sta...@dpdk.org>; dev
><dev@dpdk.org>; Akhil Goyal <gak...@marvell.com>; Jerin Jacob
>Kollanukkaran <jer...@marvell.com>
>Subject: [EXT] Re: [PATCH 01/12] common/cpt: fix build with GCC 12
>
>External Email
>
>----------------------------------------------------------------------
>Hello maintainers,
>
>On Wed, May 18, 2022 at 12:17 PM David Marchand
><david.march...@redhat.com> wrote:
>>
>> GCC 12 raises the following warning:
>>
>> In function ‘fill_sg_comp_from_iov’,
>> inlined from ‘cpt_kasumi_enc_prep’ at
>> ../drivers/common/cpt/cpt_ucode.h:2176:8,
>> inlined from ‘cpt_fc_enc_hmac_prep’ at
>> ../drivers/common/cpt/cpt_ucode.h:2475:3,
>> inlined from ‘fill_digest_params’ at
>> ../drivers/common/cpt/cpt_ucode.h:3548:14,
>> inlined from ‘otx_cpt_enq_single_sym’ at
>> ../drivers/crypto/octeontx/otx_cryptodev_ops.c:541:9,
>> inlined from ‘otx_cpt_enq_single_sym_sessless’ at
>> ../drivers/crypto/octeontx/otx_cryptodev_ops.c:584:8,
>> inlined from ‘otx_cpt_enq_single’ at
>> ../drivers/crypto/octeontx/otx_cryptodev_ops.c:611:11,
>> inlined from ‘otx_cpt_pkt_enqueue’ at
>> ../drivers/crypto/octeontx/otx_cryptodev_ops.c:643:9,
>> inlined from ‘otx_cpt_enqueue_sym’ at
>> ../drivers/crypto/octeontx/otx_cryptodev_ops.c:668:9:
>> ../drivers/common/cpt/cpt_ucode.h:415:36: error: array subscript 0 is
>> outside array bounds of ‘buf_ptr_t[0]’ {aka ‘struct buf_ptr[]’}
>> [-Werror=array-bounds]
>> 415 | e_dma_addr = bufs[j].dma_addr;
>> | ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
>> ../drivers/common/cpt/cpt_ucode.h:416:48: error: array subscript 0 is
>> outside array bounds of ‘buf_ptr_t[0]’ {aka ‘struct buf_ptr[]’}
>> [-Werror=array-bounds]
>> 416 | e_len = (size > bufs[j].size) ?
>> | ~~~~~~~^~~~~
>>
>> For now, waive this warning until we have a proper fix.
>
>Both common/cpt and crypto/cnxk have the same code that triggers this
>warning.
>Can you look into this please?
We will look into the issues in common/cpt and crypto/cnxk.
>
>Thanks.
>
>--
>David Marchand
Regards,
Ankur
