From: "John Packer" <john@sockfarm.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] A quite amusing thing...
Date: Sat, 22 Feb 2003 22:53:45 -0500 [thread overview]
Message-ID: <cdf2876c09b75531ef1d03c747bf5cf4@sockfarm.net> (raw)
In-Reply-To: <000601c2daa7$17972450$270363d9@makr4j0ty5i9an>
> Hmm... It is possible too that Amoeba developer's have copied this code
> but I doubt it.
You were joking, right?
It is telling that the comment uses the 8a assembler instructions
MOVL, AAM, and LOOP:
/*
* measure time for the loop
*
* MOVL loops,CX
* aaml1: AAM
* LOOP aaml1
*
* the time for the loop should be independent of external
* cache and memory system since it fits in theexecution
* prefetch buffer.
*
*/
next prev parent reply other threads:[~2003-02-23 3:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-22 19:17 Maksim Radziwill
2003-02-22 20:30 ` Russ Cox
2003-02-22 20:51 ` David Presotto
2003-02-23 2:16 ` Skip Tavakkolian
2003-02-23 3:53 ` John Packer [this message]
2003-02-23 6:10 ` northern snowfall
2003-02-23 8:30 ` John Packer
2003-02-23 20:26 ` northern snowfall
2003-02-23 21:28 ` John Packer
2003-02-23 22:00 ` northern snowfall
2003-02-22 20:34 philw
2003-02-22 20:40 ` Russ Cox
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=cdf2876c09b75531ef1d03c747bf5cf4@sockfarm.net \
--to=john@sockfarm.net \
--cc=9fans@cse.psu.edu \
/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).