linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.2-rc4
Date: Mon, 16 Jan 2023 10:50:33 -0800	[thread overview]
Message-ID: <20230116185033.GA2027409@roeck-us.net> (raw)
In-Reply-To: <20230116122924.116745-1-geert@linux-m68k.org>

On Mon, Jan 16, 2023 at 01:29:24PM +0100, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v6.2-rc4[1] compared to v6.1[2].
> 
...
>   + /kisskb/src/drivers/media/platform/nxp/imx-jpeg/mxc-jpeg.c: error: array subscript 2 is above array bounds of 'u32[2]' {aka 'unsigned int[2]'} [-Werror=array-bounds]:  => 641:28
>   + /kisskb/src/drivers/media/platform/nxp/imx-jpeg/mxc-jpeg.c: error: array subscript 3 is above array bounds of 'u32[2]' {aka 'unsigned int[2]'} [-Werror=array-bounds]:  => 641:28

Unless I am missing something, the code is

        for (i = fmt->mem_planes; i < fmt->comp_planes; i++)
                size += q_data->sizeimage[i];

and both mem_planes and comp_planes are <= 2. How does the compiler
calculate an error subscript of 2/3 ?

Guenter

  parent reply	other threads:[~2023-01-16 18:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-15 15:29 Linux 6.2-rc4 Linus Torvalds
2023-01-16 12:29 ` Build regressions/improvements in v6.2-rc4 Geert Uytterhoeven
2023-01-16 12:36   ` Geert Uytterhoeven
2023-01-16 16:40     ` Heiko Carstens
2023-01-16 18:41       ` Guenter Roeck
2023-01-17  8:57         ` Heiko Carstens
2023-01-17  9:03           ` Guenter Roeck
2023-01-16 18:50   ` Guenter Roeck [this message]
2023-01-16 18:52 ` Linux 6.2-rc4 Guenter Roeck
2023-01-16 18:57   ` Linus Torvalds

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=20230116185033.GA2027409@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.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).