From: "Arnd Bergmann" <arnd@arndb.de>
To: "Naresh Kamboju" <naresh.kamboju@linaro.org>,
linux-fsdevel@vger.kernel.org,
"open list" <linux-kernel@vger.kernel.org>,
regressions@lists.linux.dev, lkft-triage@lists.linaro.org,
"Linux-sh list" <linux-sh@vger.kernel.org>
Cc: "Miklos Szeredi" <mszeredi@redhat.com>,
"Ian Kent" <raven@themaw.net>,
"Christian Brauner" <brauner@kernel.org>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>,
"Rich Felker" <dalias@libc.org>,
"Yoshinori Sato" <ysato@users.sourceforge.jp>
Subject: Re: SuperH: fs/namespace.c: In function '__se_sys_listmount': syscalls.h:258:9: internal compiler error: in change_address_1, at emit-rtl.c:2275
Date: Tue, 21 Nov 2023 16:05:17 +0100 [thread overview]
Message-ID: <b78e0487-d9e7-4584-8d6b-7de119ee7769@app.fastmail.com> (raw)
In-Reply-To: <CA+G9fYvcaozQvas-h55FPjXk+uomF2CyeYbWGCsXM8yGo4SZgA@mail.gmail.com>
On Tue, Nov 21, 2023, at 15:25, Naresh Kamboju wrote:
> The SuperH tinyconfig and allnoconfig builds started failing from 20231120 tag
> Please find the following builds warnings / errors.
>
> /builds/linux/include/linux/syscalls.h:233:9: note: in expansion of
> macro '__SYSCALL_DEFINEx'
> 233 | __SYSCALL_DEFINEx(x, sname, __VA_ARGS__)
> | ^~~~~~~~~~~~~~~~~
> /builds/linux/include/linux/syscalls.h:225:36: note: in expansion of
> macro 'SYSCALL_DEFINEx'
> 225 | #define SYSCALL_DEFINE4(name, ...) SYSCALL_DEFINEx(4, _##name,
> __VA_ARGS__)
> | ^~~~~~~~~~~~~~~
> /builds/linux/fs/namespace.c:5019:1: note: in expansion of macro
> 'SYSCALL_DEFINE4'
> 5019 | SYSCALL_DEFINE4(listmount, const struct mnt_id_req __user *, req,
> | ^~~~~~~~~~~~~~~
> 0x129d9d7 internal_error(char const*, ...)
> ???:0
> 0x5dbc4d fancy_abort(char const*, int, char const*)
> ???:0
> 0x7ddd3e adjust_address_1(rtx_def*, machine_mode, poly_int<1u, long>,
> int, int, int, poly_int<1u, long>)
> ???:0
> 0x81dd91 output_operand(rtx_def*, int)
> ???:0
> 0x81e5a4 output_asm_insn(char const*, rtx_def**)
> ???:0
> 0x8226a8 final_scan_insn(rtx_insn*, _IO_FILE*, int, int, int*)
> ???:0
> Please submit a full bug report,
> with preprocessed source if appropriate.
> Please include the complete backtrace with any bug report.
> See <file:///usr/share/doc/gcc-11/README.Bugs> for instructions.
It's clearly a compiler bug, and I get the same thing with
all sh4 compilers I have on my machine, I tried with gcc-7.5
through gcc-13.
I also see that the defconfigs work fine, so it's probably
just hitting some weird corner case. You could try opening
a bug report against gcc, but I'm not sure it's worth it.
Arnd
next prev parent reply other threads:[~2023-11-21 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 14:25 Naresh Kamboju
2023-11-21 15:05 ` Arnd Bergmann [this message]
2023-11-21 15:09 ` John Paul Adrian Glaubitz
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=b78e0487-d9e7-4584-8d6b-7de119ee7769@app.fastmail.com \
--to=arnd@arndb.de \
--cc=brauner@kernel.org \
--cc=dalias@libc.org \
--cc=dan.carpenter@linaro.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mszeredi@redhat.com \
--cc=naresh.kamboju@linaro.org \
--cc=raven@themaw.net \
--cc=regressions@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
--cc=ysato@users.sourceforge.jp \
/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
all inboxes | Powered by JetHome®