[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240605062548.GF279426@thelio-3990X>
Date: Tue, 4 Jun 2024 23:25:48 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Xi Ruoyao <xry111@...111.site>
Cc: Huacai Chen <chenhuacai@...nel.org>, WANG Xuerui <kernel@...0n.name>,
Tiezhu Yang <yangtiezhu@...ngson.cn>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Bill Wendling <morbo@...gle.com>,
Justin Stitt <justinstitt@...gle.com>,
Youling Tang <tangyouling@...inos.cn>,
Jinyang He <hejinyang@...ngson.cn>, loongarch@...ts.linux.dev,
linux-kernel@...r.kernel.org, llvm@...ts.linux.dev,
mengqinggang@...ngson.cn, cailulu@...ngson.cn, wanglei@...ngson.cn,
luweining@...ngson.cn, Yujie Liu <yujie.liu@...el.com>,
Heng Qi <hengqi@...ux.alibaba.com>, Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH] loongarch: Only select HAVE_OBJTOOL and allow ORC
unwinder if the inline assembler supports R_LARCH_{32,64}_PCREL
On Wed, Jun 05, 2024 at 01:54:24PM +0800, Xi Ruoyao wrote:
> On Tue, 2024-06-04 at 22:43 -0700, Nathan Chancellor wrote:
> > For what it's worth, I have noticed some warnings with clang that I
> > don't see with GCC but I only filed an issue on our GitHub and never
> > followed up on the mailing list, so sorry about that.
> >
> > https://github.com/ClangBuiltLinux/linux/issues/2024
> >
> > Might be tangential to this patch though but I felt it was worth
> > mentioning.
>
> The warnings in GCC build is definitely the issue handled by this patch.
> But the warnings in Clang build should be a different issue. Can you
> attach the kernel/events/core.o file from the Clang build for analysis?
> I guess we need to disable more optimization...
Sure thing. Let me know if there are any issues with the attachment.
Cheers,
Nathan
Download attachment "core.o" of type "application/octet-stream" (270384 bytes)
Powered by blists - more mailing lists