9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bruce Ellis <brucee@chunder.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] brucee's 8c on sources?
Date: Fri, 14 May 2004 12:57:46 +1000	[thread overview]
Message-ID: <40A435AA.3030908@chunder.com> (raw)
In-Reply-To: <ee9e417a04051313135a2c320e@mail.gmail.com>

see http://www.chunder.com/plan9/ for some details.

basically any expression that involves vlongs, when
compiled using the default library vlong stuff, does
it's fair share of moving data on and off the stack
and calling generic functions.  a complex vlong expr
can produce pages of code.  the new 8c generates
native instructions and uses registers for most ops.
another good speedup is a simple vlong assignment,
which used to be MOVL; CLD; REP; MOVSL; and is now
MOVL; MOVL - the former suffers from many cycles of
setup.  it is probably worth extending this to copies
of larger structures but the tradeoff depends on the
flavour of x86.

why fossil?  well it is very vlongy.

brucee

Russ Cox wrote:

>>given the speed improvements fossil exhibits when compiled with the
>>new 8c i'd very much like to recompile my kernels with it :).
>
> Really?  How much improved?  What's improved?  Latency?
> It surprises me that 64-bit computation was a bottleneck,
> even in fossil.



  reply	other threads:[~2004-05-14  2:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 19:27 andrey mirtchovski
2004-05-13 20:00 ` jmk
2004-05-13 20:02   ` boyd, rounin
2004-05-13 20:13 ` Russ Cox
2004-05-14  2:57   ` Bruce Ellis [this message]
2004-05-14  5:30     ` C H Forsyth

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=40A435AA.3030908@chunder.com \
    --to=brucee@chunder.com \
    --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).