From: Sam Ravnborg <sam@ravnborg.org>
To: George Spelvin <linux@horizon.com>
Cc: akpm@linux-foundation.org, peterz@infradead.org,
zengzhaoxiu@163.com, dalias@libc.org, davem@davemloft.net,
deller@gmx.de, geert@linux-m68k.org, ink@jurassic.park.msu.ru,
james.hogan@imgtec.com, jejb@parisc-linux.org,
jonas@southpole.se, lennox.wu@gmail.com, lftan@altera.com,
linux-alpha@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
linux-metag@vger.kernel.org, linux-mips@linux-mips.org,
linux-parisc@vger.kernel.org, linux-sh@vger.kernel.org,
linux@arm.linux.org.uk, liqin.linux@gmail.com,
mattst88@gmail.com, monstr@monstr.eu,
nios2-dev@lists.rocketboards.org, ralf@linux-mips.org,
rth@twiddle.net, sparclinux@vger.kernel.org,
uclinux-h8-devel@lists.sourceforge.jp,
ysato@users.sourceforge.jp, zhaoxiu.zeng@gmail.com
Subject: Re: [patch V3] lib: GCD: add binary GCD algorithm
Date: Thu, 28 Apr 2016 21:54:06 +0200 [thread overview]
Message-ID: <20160428195326.GB29802@ravnborg.org> (raw)
In-Reply-To: <20160428164856.10120.qmail@ns.horizon.com>
> __ffs on the available architectures:
> Alpha: sometimes (CONFIG_ALPHA_EV6, CONFIG_ALPHA_EV67)
> ARC: sometimes (!CONFIG_ISA_ARCOMPACT)
> ARM: sometimes (V5+)
> ARM64: NO, could be written using RBIT and CLZ
> AVR: yes
> Blackfin: NO, could be written using hweight()
> C6x: yes
> CRIS: NO
> FR-V: yes
> H8300: NO
> Hexagon: yes
> IA64: yes
> M32R: NO
> M68k: sometimes
> MetaG: NO
> Microblaze: NO
> MIPS: sometimes
> MN10300: yes
> OpenRISC: NO
> PA-RISC: NO? Interesting code, but I think it's a net loss.
> PowerPC: yes
> S390: sometimes (CONFIG_HAVE_MARCH_Z9_109_FEATURES)
> Score: NO
> SH: NO
> SPARC: NO
SPARC: sparc64: YES, sparc32: NO
Patch needs to be updated to refelct this.
Sam
next prev parent reply other threads:[~2016-04-28 19:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 11:43 [patch V3] lib: GCD: add binary GCD algorithm zengzhaoxiu
2016-04-28 12:18 ` kbuild test robot
2016-04-28 16:48 ` George Spelvin
2016-04-28 17:51 ` Geert Uytterhoeven
2016-04-28 17:51 ` Geert Uytterhoeven
2016-04-28 17:58 ` Rich Felker
2016-04-28 17:58 ` Rich Felker
2016-04-28 18:11 ` Geert Uytterhoeven
2016-04-28 18:11 ` Geert Uytterhoeven
2016-04-28 19:15 ` George Spelvin
2016-04-28 19:54 ` Sam Ravnborg [this message]
2016-04-28 17:10 ` Josh Juran
2016-04-28 17:22 ` James Bottomley
2016-05-20 10:27 ` kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160428195326.GB29802@ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=dalias@libc.org \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=geert@linux-m68k.org \
--cc=ink@jurassic.park.msu.ru \
--cc=james.hogan@imgtec.com \
--cc=jejb@parisc-linux.org \
--cc=jonas@southpole.se \
--cc=lennox.wu@gmail.com \
--cc=lftan@altera.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-metag@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@horizon.com \
--cc=liqin.linux@gmail.com \
--cc=mattst88@gmail.com \
--cc=monstr@monstr.eu \
--cc=nios2-dev@lists.rocketboards.org \
--cc=peterz@infradead.org \
--cc=ralf@linux-mips.org \
--cc=rth@twiddle.net \
--cc=sparclinux@vger.kernel.org \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--cc=ysato@users.sourceforge.jp \
--cc=zengzhaoxiu@163.com \
--cc=zhaoxiu.zeng@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox