From: Andreas Schwab <schwab@linux-m68k.org>
To: George Spelvin <linux@horizon.com>
Cc: akpm@linux-foundation.org, dalias@libc.org, davem@davemloft.net,
geert@linux-m68k.org, James.Bottomley@HansenPartnership.com,
jjuran@gmail.com, peterz@infradead.org, sam@ravnborg.org,
zengzhaoxiu@163.com, deller@gmx.de, heiko.carstens@de.ibm.com,
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-s390@vger.kernel.org,
linux-sh@vger.kernel.org, linux-snps-arc@lists.infradead.org,
linux@arm.linux.org.uk, linux@lists.openrisc.net,
liqin.linux@gmail.com, mattst88@gmail.com, monstr@monstr.eu,
nios2-dev@lists.rocketboards.org, ralf@linux-mips.org,
rth@twiddle.net, schwidefsky@d
Subject: Re: [patch V4] lib: GCD: Use binary GCD algorithm instead of Euclidean
Date: Sat, 07 May 2016 12:46:11 +0200 [thread overview]
Message-ID: <87d1oyrvrg.fsf@linux-m68k.org> (raw)
In-Reply-To: <20160507084129.7284.qmail@ns.horizon.com> (George Spelvin's message of "7 May 2016 04:41:29 -0400")
"George Spelvin" <linux@horizon.com> writes:
> Your benchmark code doesn't have to have a separate code path if
> __x86_64__; rdtsc works on 32-bit code just as well.
Take a look at the CC: list.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2016-05-07 10:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 9:42 [patch V4] lib: GCD: Use binary GCD algorithm instead of Euclidean zengzhaoxiu
2016-05-06 23:00 ` Andrew Morton
2016-05-07 8:41 ` George Spelvin
2016-05-07 10:46 ` Andreas Schwab [this message]
2016-05-08 12:52 ` Zhaoxiu Zeng
2016-05-07 11:23 ` Sam Ravnborg
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=87d1oyrvrg.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=dalias@libc.org \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=geert@linux-m68k.org \
--cc=heiko.carstens@de.ibm.com \
--cc=ink@jurassic.park.msu.ru \
--cc=james.hogan@imgtec.com \
--cc=jejb@parisc-linux.org \
--cc=jjuran@gmail.com \
--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-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@horizon.com \
--cc=linux@lists.openrisc.net \
--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=sam@ravnborg.org \
--cc=schwidefsky@d \
--cc=zengzhaoxiu@163.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;
as well as URLs for NNTP newsgroup(s).