[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <64955942-274c-047d-aab3-308fbbe6dfbc@xen0n.name>
Date: Sat, 24 Jun 2023 01:06:59 +0800
From: WANG Xuerui <kernel@...0n.name>
To: Xi Ruoyao <xry111@...111.site>, Huacai Chen <chenhuacai@...nel.org>
Cc: WANG Rui <wangrui@...ngson.cn>, loongarch@...ts.linux.dev,
linux-kbuild@...r.kernel.org, llvm@...ts.linux.dev,
linux-kernel@...r.kernel.org, WANG Xuerui <git@...0n.name>
Subject: Re: [PATCH 7/9] LoongArch: Tweak CFLAGS for Clang compatibility
On 6/24/23 01:00, Xi Ruoyao wrote:
> On Fri, 2023-06-23 at 21:43 +0800, WANG Xuerui wrote:
>
>> -cflags-y += -G0 -pipe -msoft-float
> -msoft-float should not be removed. Our consensus (made when I was
> developing https://gcc.gnu.org/r13-6500) is -mabi=lp64s does *not*
> disable floating point instructions, but only disable FPRs for passing
> arguments and return values. So w/o -msoft-float (or -mfpu=none) GCC is
> allowed to generate FP instructions everywhere in kernel and it may
> cause kernel FPD exception in the future.
Hmm, now I remember (still vaguely) about the discussion... I'll have to
check how to minimize churn around FPU-touching code though if
-msoft-float is to be kept.
--
WANG "xen0n" Xuerui
Linux/LoongArch mailing list: https://lore.kernel.org/loongarch/
Powered by blists - more mailing lists