linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-um@lists.infradead.org,
	linux-spi@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.4-rc6
Date: Mon, 12 Jun 2023 12:08:50 +0200	[thread overview]
Message-ID: <CAMuHMdXUz5KatvuDxPZN5YEP-8SrqonbGCO-411CxWuKQn1PXA@mail.gmail.com> (raw)
In-Reply-To: <ea22bff7-ecd2-018e-77a1-1d2edaa21355@linaro.org>

Hi Tudor,

On Mon, Jun 12, 2023 at 11:48 AM Tudor Ambarus <tudor.ambarus@linaro.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@linux-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

      reply	other threads:[~2023-06-12 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-11 21:53 Linux 6.4-rc6 Linus Torvalds
2023-06-12  9:09 ` Build regressions/improvements in v6.4-rc6 Geert Uytterhoeven
2023-06-12  9:28   ` Geert Uytterhoeven
2023-06-12  9:48     ` Tudor Ambarus
2023-06-12 10:08       ` Geert Uytterhoeven [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=CAMuHMdXUz5KatvuDxPZN5YEP-8SrqonbGCO-411CxWuKQn1PXA@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=tudor.ambarus@linaro.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).