From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Go: FP in note handler
Date: Tue, 23 Feb 2016 09:02:27 -0800 [thread overview]
Message-ID: <915a03201f12f2e4e5879a1f1a8b9e23@lilly.quanstro.net> (raw)
In-Reply-To: <68D3A127-CECA-4E8D-951F-756992D11710@gmail.com>
On Tue Feb 23 07:55:26 PST 2016, kennylevinsen@gmail.com wrote:
> A benchmark was supposedly made of the new duffcopy/duffzero which claimed significant speedup for larger copies: https://github.com/golang/go/commit/5cf281a9b791f0f10efd1574934cbb19ea1b33da
>
> I have no clue whether this holds true or not. My intention to reenable duffcopy and continue to use duffzero is mostly to avoid differences and ensure that the note handlers are floating point free in the future. Whether the duffcopy/duffzero’s current form is an actual optimization or just a complexity, I cannot say. A test was made in #cat-v out of annoyance where the result seemed to be that it was indeed faster to use MOVUPS, but I don’t remember the details.
that post is a speedup relative to the original asm, which might not be as good as the best
non-sse versions, and it is also for amd64.
- erik
next prev parent reply other threads:[~2016-02-23 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e115154c5bab8971d7b88f64ba5d4402@proxima.alt.za>
2016-02-23 10:17 ` Kenny Lasse Hoff Levinsen
2016-02-23 15:27 ` erik quanstrom
2016-02-23 15:52 ` Kenny Lasse Hoff Levinsen
2016-02-23 17:02 ` erik quanstrom [this message]
2016-02-23 17:14 ` Kenny Lasse Hoff Levinsen
2016-02-23 17:31 ` lucio
2016-02-23 17:56 ` Kenny Lasse Hoff Levinsen
[not found] <83031ee52a34de15facd95dcbcabbad9@proxima.alt.za>
2016-02-23 8:26 ` Kenny Lasse Hoff Levinsen
[not found] <fb16aa69c6b73a2e8f0260b4e6ee025c@hamnavoe.com>
2016-02-22 21:56 ` Kenny Lasse Hoff Levinsen
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=915a03201f12f2e4e5879a1f1a8b9e23@lilly.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).