From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-sh@vger.kernel.org, linux-um@lists.infradead.org,
linux-rdma@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: Build regressions/improvements in v5.18-rc5
Date: Mon, 2 May 2022 09:14:19 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2205020912140.658493@ramsan.of.borg> (raw)
In-Reply-To: <20220502065353.2658957-1-geert@linux-m68k.org>
On Mon, 2 May 2022, Geert Uytterhoeven wrote:
> JFYI, when comparing v5.18-rc5[1] to v5.18-rc4[3], the summaries are:
> - build errors: +6/-21
6 error regressions:
+ /kisskb/src/arch/sh/kernel/machvec.c: error: array subscript 'struct sh_machine_vector[0]' is partly outside array bounds of 'long int[1]' [-Werror=array-bounds]: => 105:33
sh4-gcc11/se7750_defconfig
sh4-gcc11/sh-defconfig
sh4-gcc11/se7619_defconfig
sh4-gcc11/sh-allmodconfig
sh4-gcc11/sh-allyesconfig
sh4-gcc11/sh-allnoconfig
gcc-11 fallout
+ /kisskb/src/drivers/infiniband/sw/rdmavt/qp.c: error: 'struct cpuinfo_um' has no member named 'x86_cache_size': => 88:22
+ /kisskb/src/drivers/infiniband/sw/rdmavt/qp.c: error: control reaches end of non-void function [-Werror=return-type]: => 89:1
+ /kisskb/src/drivers/infiniband/sw/rdmavt/qp.c: error: implicit declaration of function '__copy_user_nocache' [-Werror=implicit-function-declaration]: => 100:2
um-x86_64/um-all{yes,no}config
+ /kisskb/src/include/linux/sh_intc.h: error: division 'sizeof (void *) / sizeof (void)' does not compute the number of array elements [-Werror=sizeof-pointer-div]: => 100:63
v5.18-rc5/sh4-gcc11/se7750_defconfig
v5.18-rc5/sh4-gcc11/sh-defconfig
v5.18-rc5/sh4-gcc11/se7619_defconfig
v5.18-rc5/sh4-gcc11/sh-allmodconfig
v5.18-rc5/sh4-gcc11/sh-allyesconfig
v5.18-rc5/sh4-gcc11/sh-allnoconfig
gcc-10/11 fallout, seen before for sh4-gcc10/se7750_defconfig and sh4-gcc10/se7619_defconfig
+ {standard input}: Error: branch to a symbol in another ISA mode: => 1295
mips-gcc11/micro32r2_defconfig
mips-gcc11/micro32r2el_defconfig
gcc-11 fallout
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/672c0c5173427e6b3e2a9bbb7be51ceeec78093a/ (all 138 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/af2d861d4cd2a4da5137f795ee3509e6f944a25b/ (96 out of 138 configs)
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
parent reply other threads:[~2022-05-02 7:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220502065353.2658957-1-geert@linux-m68k.org>]
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=alpine.DEB.2.22.394.2205020912140.658493@ramsan.of.borg \
--to=geert@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-um@lists.infradead.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