[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1459220164.25110.41.camel@perches.com>
Date: Mon, 28 Mar 2016 19:56:04 -0700
From: Joe Perches <joe@...ches.com>
To: Zeng Zhaoxiu <zhaoxiu.zeng@...il.com>,
Sam Ravnborg <sam@...nborg.org>
Cc: Denys Vlasenko <dvlasenk@...hat.com>,
Arnd Bergmann <arnd@...db.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Martin Kepplinger <martink@...teo.de>,
Sasha Levin <sasha.levin@...cle.com>,
Ingo Molnar <mingo@...nel.org>,
Yury Norov <yury.norov@...il.com>,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH 01/31] bitops: add parity functions
On Tue, 2016-03-29 at 10:27 +0800, Zeng Zhaoxiu wrote:
> 在 2016年03月28日 14:51, Sam Ravnborg 写道:
[]
> > Defining these as static inlines in asm-generic prevent an
> > architecture
> > from selecting between a more optimal asm version or the generic version
> > at run-time.
> > sparc would benefit from this as only some sparc chips supports popc.
> > See how this is done for hweight*
> >
> > Sam
> Thanks. I will try.
You might also try to describe in any commit message
and perhaps the internal documentation why using gcc's
__builtin_parity isn't appropriate.
Powered by blists - more mailing lists