[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5de9d69817138f2ccae0867b5ccb602dcfa007a3.camel@xry111.site>
Date: Fri, 09 Jun 2023 21:05:07 +0800
From: Xi Ruoyao <xry111@...111.site>
To: Tiezhu Yang <yangtiezhu@...ngson.cn>, Arnd Bergmann <arnd@...db.de>
Cc: Linux-Arch <linux-arch@...r.kernel.org>,
linux-s390@...r.kernel.org, llvm@...ts.linux.dev,
linux-ia64@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-parisc@...r.kernel.org, x86@...nel.org,
linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org, loongarch@...ts.linux.dev,
linux-alpha@...r.kernel.org, sparclinux@...r.kernel.org,
linux-riscv@...ts.infradead.org, linuxppc-dev@...ts.ozlabs.org,
bpf@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
loongson-kernel@...ts.loongnix.cn
Subject: Re: [RFC PATCH] asm-generic: Unify uapi bitsperlong.h
On Fri, 2023-06-09 at 14:50 +0800, Tiezhu Yang wrote:
/* snip */
> > > > In musl, the documentation states that at least gcc-3.4 or
> > > > clang-3.2 are required, which probably predate the
> > > > __SIZEOF_LONG__ macro.
Indeed, I've digged some history and __SIZEOF_LONG__ was added into GCC-
4.3 (in 2008). And I didn't realize the bitsperlong.h in tools
directory is a copy from uapi.
> > > > On the other hand, musl was only
> > > > released in 2011, and building musl itself explicitly
> > > > does not require kernel uapi headers, so this may not
> > > > be too critical.
> Only arm64, riscv and loongarch belong to the newer architectures
> which are related with this change, I am not sure it is necessary
> to "unify" uapi bitsperlong.h for them.
At least it will stop the engineers working on "the next architecture"
from adding an unneeded bitsperlong.h :).
--
Xi Ruoyao <xry111@...111.site>
School of Aerospace Science and Technology, Xidian University
Powered by blists - more mailing lists