From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Thomas Gleixner <tglx@kernel.org>, <peterz@infradead.org>,
<luto@kernel.org>, <linux-kernel@vger.kernel.org>
Cc: kernel test robot <lkp@intel.com>,
<oe-kbuild-all@lists.linux.dev>,
Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [PATCH] entry: Provide stub for syscall_enter_audit() when auditing is disabled
Date: Tue, 21 Jul 2026 10:41:30 +0800 [thread overview]
Message-ID: <928b341f-0a79-4c11-9af7-06497d1ecfd2@huawei.com> (raw)
In-Reply-To: <87a4rlmrx8.ffs@fw13>
On 7/21/2026 2:34 AM, Thomas Gleixner wrote:
> On Mon, Jul 20 2026 at 17:34, Thomas Gleixner wrote:
>> On Mon, Jul 20 2026 at 17:49, Jinjie Ruan wrote:
>> The .config in the report builds without problems with s390-linux-gcc
>> 15.2.0 (I verified that before merging), but fails with the version used
>> by the robot:
>>
>> compiler: s390-linux-gcc (GCC) 13.4.0
>>
>> So that's a broken compiler and without understanding the actual root
>> cause we are not going to paper over it.
>
> What's even more amazing is that the same config modified for x86/64
> builds just fine with gcc 13.4.0, while one would assume that the
> decision to uninline a basically empty inline would happen before the
> architecture specific backend is invoked. But what do I know. :)
Yes, I also couldn't reproduce this compilation issue on x86, so it does
appear to be a compiler problem.
>
next prev parent reply other threads:[~2026-07-21 2:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 9:49 Jinjie Ruan
2026-07-20 15:34 ` Thomas Gleixner
2026-07-20 18:34 ` Thomas Gleixner
2026-07-21 2:41 ` Jinjie Ruan [this message]
2026-07-21 2:47 ` Jinjie Ruan
2026-07-21 7:58 ` Thomas Gleixner
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=928b341f-0a79-4c11-9af7-06497d1ecfd2@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luto@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=svens@linux.ibm.com \
--cc=tglx@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
Powered by JetHome