From: "Bruce Ellis" <brucee@chunder.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] new 8c
Date: Wed, 17 Mar 2004 08:55:56 +1100 [thread overview]
Message-ID: <00d501c40ba1$7c4ba930$8201a8c0@cc77109e> (raw)
I've improved the vlong support in 8c.
The missing ops are in, load/store optimizations,
and things like add, sub etc. aren't function calls.
A simple test (summing a large array of random
vlongs) shows a factor of 3 speed up on my
machine (braindead PII) so maybe I haven't been
just wasting time.
It's not ready for public consumption yet but I
have thrown a copy at presto and jmk.
I'll put it on my web-site in a few days.
Reading x86 assemb, let alone generating it is
starting to get to me.
brucee
next reply other threads:[~2004-03-16 21:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 21:55 Bruce Ellis [this message]
2004-03-16 21:56 ` Sape Mullender
2004-03-16 23:08 ` Bruce Ellis
2004-03-17 3:27 ` Sape Mullender
2004-03-16 22:09 ` boyd, rounin
2004-04-07 2:26 Bruce Ellis
2004-05-02 1:15 Bruce Ellis
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='00d501c40ba1$7c4ba930$8201a8c0@cc77109e' \
--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).