From: "Bruce Ellis" <brucee@chunder.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] 8c vlong support
Date: Sun, 28 Mar 2004 18:47:28 +1000 [thread overview]
Message-ID: <002101c414a1$52f33fe0$8201a8c0@cc77109e> (raw)
In-Reply-To: <200403280655.i2S6tSGP092599@adat.davidashen.net>
i have been doing a fair amount of vlong support for 8c.
it's all table driven and fraught with peril.
it compiles itself to a fixed point and passed all the torture
tests i thru at it. jmk did some testing and found a nasty,
which is fixed, and now he reports that the kernel runs
just fine.
i'd like bashers - break it please and you get a beer.
should i post a URL now or is it better for me to find
some more bugs (and write some more tables) and post
it next week?
humbly and stumbly,
brucee
next prev parent reply other threads:[~2004-03-28 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-27 21:33 [9fans] kernels on sources Micah Stetson
2004-03-28 1:17 ` andrey mirtchovski
2004-03-28 6:15 ` Micah Stetson
2004-03-28 6:55 ` David Tolpin
2004-03-28 8:47 ` Bruce Ellis [this message]
2004-03-28 8:54 ` [9fans] 8c vlong support 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='002101c414a1$52f33fe0$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).