[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1606282041350.12650@digraph.polyomino.org.uk>
Date: Tue, 28 Jun 2016 20:46:05 +0000
From: Joseph Myers <joseph@...esourcery.com>
To: Yury Norov <ynorov@...iumnetworks.com>
CC: <libc-alpha@...rceware.org>, <linux-kernel@...r.kernel.org>,
<arnd@...db.de>, <catalin.marinas@....com>,
<marcus.shawcroft@....com>, <philb@....org>, <davem@...emloft.net>,
<szabolcs.nagy@....com>, <maxim.kuvyrkov@...aro.org>,
<pinskia@...il.com>, <bamvor.zhangjian@...wei.com>,
<schwab@...e.de>, <fweimer@...hat.com>, <Prasun.Kapoor@...ium.com>,
<cmetcalf@...lanox.com>, <hjl.tools@...il.com>,
<adhemerval.zanella@...aro.org>, Yury Norov <yury.norov@...il.com>
Subject: Re: [PATCH 18/23] [AARCH64] ILP32: support stat syscall family
On Tue, 28 Jun 2016, Yury Norov wrote:
> What you talk about sounds unclear to me. If you mean to unify with
> one of existing ports, it looks unnecessary, as ilp32 will end up with
> RISC-V anyway. If you mean to use RISC-V, it's not ready yet. I was
> thinking that when they will finish, they simply switch this port to
> their code. Am I too optimistic?
I mean unify in sysdeps/unix/sysv/linux (or .../generic if inappropriate
for the main sysdeps/unix/sysv/linux), for all architectures, both
existing and new, with conditionals based on logical features of the
architectures. If any architecture has its own implementation, it should
only be old architectures with their special peculiarities.
> Is there glibc analogue for kernel scripts/checkpatch.pl? If yes,
> please point me out, and I'll briefly fix all issues. If no please be
I'm not aware of an analogue, although GCC's contrib/check_GNU_style.sh
may well be helpful for some issues.
--
Joseph S. Myers
joseph@...esourcery.com
Powered by blists - more mailing lists