From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] FTQ benchmark available
Date: Sat, 12 Apr 2008 10:18:36 +0100 [thread overview]
Message-ID: <079c1523b54b123fb0e587ed84a87098@terzarima.net> (raw)
In-Reply-To: <F48976A4-C55E-40DE-A4C5-75D07FE1F021@mac.com>
> Seriously: what's the point?
i'm sometimes interested in seeing the differences (if any) caused
by certain system changes, with a view to showing that you can be
fast but still straightforward and sane, without a load of ugly code
let alone inlined assembly code and 60,000 lines of include files.
next prev parent reply other threads:[~2008-04-12 9:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 17:09 john
2008-04-10 17:22 ` andrey mirtchovski
2008-04-10 17:28 ` john
2008-04-10 17:58 ` ron minnich
2008-04-10 18:25 ` Charles Forsyth
2008-04-10 18:30 ` ron minnich
2008-04-10 21:05 ` andrey mirtchovski
2008-04-10 21:28 ` john
2008-04-10 21:33 ` andrey mirtchovski
2008-04-11 1:13 ` ron minnich
2008-04-11 2:15 ` erik quanstrom
2008-04-11 3:17 ` ron minnich
2008-04-12 0:23 ` dave.l
2008-04-12 0:35 ` ron minnich
2008-04-12 0:38 ` John Floren
2008-04-13 17:58 ` dave.l
2008-04-12 9:18 ` Charles Forsyth [this message]
2008-04-10 19:39 Matthew Sottile
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=079c1523b54b123fb0e587ed84a87098@terzarima.net \
--to=forsyth@terzarima.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).