[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <274fe4e6ff05401bc43d952efe69908fe052d875.camel@xry111.site>
Date: Sat, 25 Oct 2025 21:02:45 +0800
From: Xi Ruoyao <xry111@...111.site>
To: Guenter Roeck <linux@...ck-us.net>, Huacai Chen <chenhuacai@...nel.org>
Cc: Nathan Chancellor <nathan@...nel.org>, Huacai Chen
<chenhuacai@...ngson.cn>, loongarch@...ts.linux.dev, Xuefeng Li
<lixuefeng@...ngson.cn>, Guo Ren <guoren@...nel.org>, Xuerui Wang
<kernel@...0n.name>, Jiaxun Yang <jiaxun.yang@...goat.com>,
linux-kernel@...r.kernel.org, stable@...r.kernel.org, Binbin Zhou
<zhoubinbin@...ngson.cn>
Subject: Re: [PATCH V2] LoongArch: Align ACPI structures if
ARCH_STRICT_ALIGN enabled
On Fri, 2025-09-26 at 11:27 -0700, Guenter Roeck wrote:
> > > I see that the patch made it into the upstream kernel, now breaking both
> > > mainline and 6.16.y test builds of loongarch64:allmodconfig with gcc.
> > >
> > > Since this is apparently intentional, I'll stop build testing
> > > loongarch64:allmodconfig. So far it looks like my qemu tests
> > > are not affected, so I'll continue testing those for the time being.
> >
> > See https://gcc.gnu.org/PR122073 and
> > https://github.com/acpica/acpica/pull/1050.
> >
>
> I understand that. Every compiler has bugs. Normally workarounds are implemented.
> Since that won't happen here, my remedy is to stop testing the affected
> configuration(s). I do this whenever I learn that a known problem won't be fixed.
> The above is not a complaint, just an information.
Hi Guenter,
The mainline should be already fixed with 6e3a4754717a ("ACPICA: Work
around bogus -Wstringop-overread warning since GCC 11") now. The commit
is Cc'ed to stable so we can expect 6.16.y will be fixed soon as well.
--
Xi Ruoyao <xry111@...111.site>
Powered by blists - more mailing lists