From: Gregory Maxwell <greg@xiph.org>
To: Cory Fields <lists@coryfields.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Cc: "Radcliffe, Mark" <Mark.Radcliffe@dlapiper.com>,
"Roay, Leslie" <Leslie.Roay@dlapiper.com>
Subject: Re: [bitcoin-dev] Bitcoin Assistance
Date: Wed, 27 Sep 2017 22:06:58 +0000 [thread overview]
Message-ID: <CAAS2fgQpmNHaUWHTG-NXeW4+W01yRp47EVB_HcK4Pn3GDoTHzg@mail.gmail.com> (raw)
In-Reply-To: <CAApLimhdKtQnx4CPwRsiB0LiOiWAQxJds3MhumXRqSpfMnEMnQ@mail.gmail.com>
On Wed, Sep 27, 2017 at 9:20 PM, Cory Fields via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
>> License for A fast alternative to the modulo reduction
>
> This references a comment cuckoocache.h. No code from the site is used. The
> link to the site was added after the code, as the site provides a helpful
> explanation for the technique used.
As the author of that comment: the reference there is unrelated to the
code but just a found-on-the-internet explanation for an trivial, old,
and well known technique (which I've seen in code since at least the
80s) that manages to sometimes surprise people who aren't familiar
with fixed point signal processing. I wrote and submitted the comment
after encountering people confused by our code in another project,
long after it was written.
prev parent reply other threads:[~2017-09-27 22:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 21:53 [bitcoin-dev] Bitcoin Assistance Radcliffe, Mark
2017-09-26 13:12 ` Omar Shibli
2017-09-27 21:20 ` Cory Fields
2017-09-27 21:54 ` Tim Ruffing
2017-09-27 22:21 ` Gregory Maxwell
2017-09-27 22:41 ` Tim Ruffing
2017-09-27 22:06 ` Gregory Maxwell [this message]
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=CAAS2fgQpmNHaUWHTG-NXeW4+W01yRp47EVB_HcK4Pn3GDoTHzg@mail.gmail.com \
--to=greg@xiph.org \
--cc=Leslie.Roay@dlapiper.com \
--cc=Mark.Radcliffe@dlapiper.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=lists@coryfields.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