| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
updated dates on files that have actually changed this year. This makes
the diff across versions readable again.
|
| |
|
|
|
|
| |
Monotone mailing list, it was needed for a build.
|
|
|
|
|
| |
expansion. While I would prefer to have the compiler to this, using GCC 4.1.2
it is 4% faster on a Core2 Q6600 with the loops partially unrolled.
|
|
|
|
|
|
|
|
| |
takes advantage of unaligned reads/writes being legal for some extra performance,
but should be rewritten to use SSE2 and non-termporal writes.
Most of the functions in bit_ops.cpp are implemented by x86-64, just not
easily accessible from C++
|
|
|
|
| |
DEFAULT_BUFFERSIZE (normally 4K); measurably faster on a Core2
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the word read/write functions will be faster through the use of
(slightly unsafe) pointer manipulations. On some CPUs (like SPARC),
these antics can cause crashes (usually visible by SIGBUS) if what you
are attempting to read or write as an integer is not aligned on a word
boundary. However they are safe on x86 and x86-64.
Performance increases across the board on a Core2. In most algorithms
the improvement seems to be about 3%, except a few standouts like RC6
(15%), MD4 (20%), RIPEMD-128 (8%). Will be better with faster xor_buf
and byte swapping.
|
| |
|
|
|
|
| |
harmless, to avoid a valgrind warning
|
|
|
|
| |
wrong, and didn't work at all. New corrected (and tested) version.
|
|
|
|
|
|
|
| |
with the last one being both one of the input values and the output carry
register, since almost always they were in fact the same variable.
Also update the x86 and x86-64 modules.
|
|
|
|
| |
writing of it in assembly.
|
|
|
|
|
|
|
| |
for 64-bit to not use 64-bit constants - that way GCC won't complain everwhere.
Plan is for a module to replace all of these with asm (bswap, xchg on x86),
at least for x86-64
|
|
|
|
|
|
|
| |
but might as well keep it up to date. And it's easier to do it once with
a 'perl -pi' command than to update each file over time.
Apologies to anyone looking at diffs.
|
|
|
|
| |
fewer explicit coercions.
|
|
|
|
| |
for struct stat
|
|
|
|
|
|
|
| |
Has not been tested on all of the systems listed, and on many of them it
won't be relevant anyway since /dev/random and company only exist on some
of them (Linux, BSDs, recent Solaris, and it looks like recent AIX and
HP-UX as well).
|
| |
|
| |
|
|
|
|
| |
commonly used options are near the top.
|
| |
|
|\
| |
| |
| | |
and '9fe0310805932b889bdfa17c9213f2b97d47ab6a'
|
| |
| |
| |
| |
| |
| | |
explicit :: (it is unfortunate that there is no good way to detect all
of such calls in an automated manner). Also use new-style casts in parts
of the zlib code.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
/dev/urandom /dev/random
to
/dev/random /dev/srandom /dev/urandom
because the es_dev module can handle reads from devices that may block
without ever blocking for an unbounded amount of time.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
iostreams, it uses unbuffered Unix I/O syscalls and is careful to avoid
blocking for more than short amounts of time.
|
| | |
|
| | |
|
| |
| |
| |
| | |
after assignment.
|
| |
| |
| |
| |
| |
| | |
by Joel Low on the mailing list, the STL container types have only a
single version of push_back(), along with variations of insert() for
handling range-based appending.
|
| |
| |
| |
| |
| | |
doesn't go beyond that. Since 1.4 itself is pretty obsolete, and 1.6
is now in wide use, just drop the doc in mainline
|
| | |
|
| |
| |
| |
| | |
Change all callers in the library and self-test code.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
needing this functionality probably already have a preexisting configuration
system that they would rather use.
Also remove the documentation about this feature, and the example
configuration (which was pretty out of date, anyway).
RFC on this change sent to the mailing list on 11-13-2007, no responses
after 24 hours. It seems quite likely this code is not in use anywhere.
|
| |\
| | |
| | |
| | | |
and '9f004fd94273d5449388f933f767d6d5c24068d8'
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
had no reason/need to be a class method.
|
| | |
| | |
| | |
| | | |
the code more readable/explicit either.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Split up some lines for readability. Benchmarks somewhat slower than the
previous version (34.3 vs 32.0 on my Core2, gcc 4.1.2), will need to
investigate.
|
| | | |
|
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Wrap lines a little tighter in the output of --help
Change the order of checks so we don't display that a module was not
used due to use of --no-asm when in fact the module would not run on
the target CPU anyway. Similiarly don't say "loaded only on request" if
it is incompatible with the target, since someone attempting to actually
load the module would immediately get an error.
|
| | |
|
| |
| |
| |
| | |
remained, which caused link errors. Removed.
|
| |\
| | |
| | |
| | | |
and '3b5a05478d1cfb7d4b10501d965228feae5b6dfa'
|
| | | |
|
| |/
| |
| |
| |
| | |
compiler. That tends to give the most useful diagnostic output, since
CPU restrictions are the most common in modules.
|