[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMuHMdXUz5KatvuDxPZN5YEP-8SrqonbGCO-411CxWuKQn1PXA@mail.gmail.com>
Date: Mon, 12 Jun 2023 12:08:50 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Tudor Ambarus <tudor.ambarus@...aro.org>
Cc: linux-kernel@...r.kernel.org, linux-um@...ts.infradead.org,
linux-spi@...r.kernel.org, linux-mips@...r.kernel.org
Subject: Re: Build regressions/improvements in v6.4-rc6
Hi Tudor,
On Mon, Jun 12, 2023 at 11:48 AM Tudor Ambarus <tudor.ambarus@...aro.org> wrote:
> On 6/12/23 10:28, Geert Uytterhoeven wrote:
> >> JFYI, when comparing v6.4-rc6[1] to v6.4-rc5[3], the summaries are:
> >> - build errors: +5/-6
> >
> > + /kisskb/src/drivers/spi/spi-stm32-qspi.c: error: ‘op’ is used
> > uninitialized [-Werror=uninitialized]: => 523:27, 564:27
>
> Seems that the report is not correct for this particular case as op is
> filled either by memcpy or memset before use.
I can reproduce the issue with gcc 12.1.0-2ubuntu1~22.04.
No idea what's wrong. Disabling CONFIG_FORTIFY_SOURCE doesn't
help. Perhaps an issue with the memcpy() used by UML?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists