DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Rasesh Mody <rmody@marvell.com>,
	Devendra Singh Rawat <dsinghrawat@marvell.com>,
	amitprakashs@marvell.com
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] net/qede/base: fix 32-bit build with GCC 12
Date: Thu, 06 Oct 2022 12:27:01 +0200	[thread overview]
Message-ID: <1803473.atdPhlSkOF@thomas> (raw)
In-Reply-To: <20221004111811.1502920-1-thomas@monjalon.net>

04/10/2022 13:18, Thomas Monjalon:
> A pointer is passed to a macro and it seems mistakenly referenced.
> This issue is seen only when compiling with GCC 12 for 32-bit:
> 
> drivers/net/qede/base/ecore_init_fw_funcs.c:1418:25:
>         error: array subscript 1 is outside array bounds of ‘u32[1]’
>         {aka ‘unsigned int[1]’} [-Werror=array-bounds]
>  1418 |                 ecore_wr(dev, ptt, ((addr) + (4 * i)),  \
>       |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  1419 |                          ((u32 *)&(arr))[i]);           \
>       |                          ~~~~~~~~~~~~~~~~~~~
> drivers/net/qede/base/ecore_init_fw_funcs.c:1465:17:
>         note: in expansion of macro ‘ARR_REG_WR’
>  1465 |         ARR_REG_WR(p_hwfn, p_ptt, addr, pData, len_in_dwords);
>       |         ^~~~~~~~~~
> drivers/net/qede/base/ecore_init_fw_funcs.c:1439:35:
>         note: at offset 4 into object ‘pData’ of size 4
>  1439 |                              u32 *pData,
>       |                              ~~~~~^~~~~
> 
> Fixes: 3b307c55f2ac ("net/qede/base: update FW to 8.40.25.0")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>

A similar patch was sent 6 weeks ago by Amit Prakash Shukla.



      parent reply	other threads:[~2022-10-06 10:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 11:18 Thomas Monjalon
2022-10-05 19:28 ` David Marchand
2022-10-06 10:27 ` Thomas Monjalon [this message]

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=1803473.atdPhlSkOF@thomas \
    --to=thomas@monjalon.net \
    --cc=amitprakashs@marvell.com \
    --cc=dev@dpdk.org \
    --cc=dsinghrawat@marvell.com \
    --cc=rmody@marvell.com \
    --cc=stable@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 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).