Bob Jenkins' Web SiteHere's a 128-bit noncryptographic hash that runs at 3 bytes/cycle for long messages. It's much slower than lookup3 for short messages. Most uses of noncryptographic hashing have mostly short messages. The code and ideas behind this hash are quite ugly, too. I'm working on a modification of frog that uses all the RAM, CPU, and disk of a machine. That works out to me belatedly learning Windows file I/O, things like "you can only have 512 files handles open at once" and "asynchronous I/O does have a callback interface" and "does I/O consume any CPU?". For example, there were too many unknowns, so I wrote a test program to explore some of these interfaces. The first thing I found out was that (printf + cygwin + gcc + Windows 98 + Windows threads) isn't threadsafe. Although (printf + Vista + cl + Windows threads) is threadsafe. Fine, here is a program with a threadsafe printf replacement for gcc. |
![]() |
Table of Contents (internal links):