| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
on a particular ISA extension rather than a list of CPUs. Much
easier to edit and audit, too. Add markers on the AES-NI code and
SHA-1/SSE2. Serpent and XTEA don't need it because they are
generic and only depend on simd_32 which will silenty swap out a
scalar version if SSE2/AltiVec isn't enabled (since it turns out
on supersclar processors just doing 4 blocks in parallel can be a
win even in GPRs).
Add pentium3 to the list of CPUs with rdtsc, was missing. Odd!
|
|
|
|
|
|
| |
ignores this unless it can detect (or is asked to use) a specific model;
otherwise it compiles for the baseline ISA. Remove the default_submodel
entries in the arch files.
|
|
|
|
|
|
|
|
| |
ISA extensions (say, Intel's AES-NI, for instance) so change everything
to reflect that.
Also rename some of the amd64 models, and add entries for k10, nehalem,
and westmere processors.
|
|
|
|
|
|
| |
SSE2, SSSE3, NEON, and AltiVec.
Add entries for Intel Atom, POWER6 and POWER7, and the Cortex A8 and A9.
|
| |
|
| |
|
|
|
|
|
| |
Pretty much useless and unused, except for listing the module names in
build.h and the short versions totally suffice for that.
|
|\
| |
| |
| |
| |
| | |
3158f8272a3582dd44dfb771665eb71f7d005339)
to branch 'net.randombit.botan' (head bf629b13dd132b263e76a72b7eca0f7e4ab19aac)
|
| |
| |
| |
| | |
seem to work with C++ at all so untested.
|
| |\
| | |
| | |
| | |
| | |
| | | |
c5ae189464f6ef16e3ce73ea7c563412460d76a3)
to branch 'net.randombit.botan' (head e2b95b6ad31c7539cf9ac0ebddb1d80bf63b5b21)
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
--use-boost-python to enable creating a second makefile, Makefile.python,
which has targets for building and installing the Python module.
|
| | |
| | |
| | |
| | | |
With GCC, only use -finline-functions if not a debug build
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
memory accesses. Since this can be a pretty big win, enable it for them.
The m68k apparently also can, except in its (modern) Coldfire version,
but it's always big endian so mark that as such.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Modify ECB to use parallel encryption/decryption where possible
Add toggles in build.h specifying how many blocks to process in parallel.
Defaults to 8 blocks for all modes, which is sufficient that any likely
parallelism can be extracted (via SIMD or concurrent execution) but not
so much as to seem likely to cause cache problems (8*128 bits = 128 bytes,
or two x86 cache lines)
|
|/ / |
|
|/
|
|
|
|
| |
such in configure.py. Paul Clark reported on the list having problems with
it otherwise because of CVS droppings being picked up and subsequently
errored on when parsing them as build info files (of course) failed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
systems. This was something that for whatever reason that I have
long since forogotten was a good idea on IRIX running MIPS circa
a decade ago, but was reported to cause problems on the Debian
builds.
Add mipsel as an alias for the mips32 architecture for Debian.
The mips32 submodel names were badly typoed and did not work
correctly.
Remove the leading mips32- and mips64- from MIPS submodel names.
|
|
|
|
|
|
|
| |
based on the SGI Pro64 and Pathscale EKOpath compilers. Only tested on an
x86-64 system running Linux (v4.2.1). Miscompiles a few of the block ciphers
(segvs, didn't bother to diagnose further; recompile with -O1 to fix), other
than that seems OK.
|
|
|
|
| |
Contributed by Patrick Georgi
|
|
|
|
|
| |
Python configure scripts. Previously Python version would give up, and
the Perl one would guess i686 (!)
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
db0cdfa10718d2065e52b6753d1d671b71cb423d)
to branch 'net.randombit.botan.python-configure' (head f106b1e4c7361a0fee6856defb01a9f96a2fd4eb)
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
had been denoted with @{var:NAME}, this has changed to %{NAME}. This is
pretty much a wash for configure.pl but it makes it much easier to process
the templates using Python's string.Template. The logic being the 'var:'
prefix had been to support conditional statements in the templates (using
an 'if:' prefix), but this functionality was not being used and support
for it is removed from configure.pl in this revision.
For a similiar reason, rename a number of template variables with hyphens
in their name to use underscores instead. This is slightly more consistent
anyway (since many variable names had already used _ instead of -) but more
importantly makes them much easier to deal with using aforementioned Python
template code.
This should not result in any user-visible change (unless I messed up).
|
|
|
|
|
|
|
|
|
|
|
| |
since they often contain spaces. This doesn't matter to configure.pl's
hand-done regex 'parser', but it makes things more consistent and makes
it possible to use the shlex parser included with python to parse all of
the data files.
Also remove the unused <arch> entry in darwin - this information had
previously be removed from all the other files but I guess that one was
missed.
|
|
|
|
|
| |
but with the most recent change to decouple version # and so version this
is wrong - use @{var:so_version} instead.
|
| |
|
|
|
|
| |
number increments, for stable releases that don't affect binary compat.
|
|
|
|
|
|
|
| |
botan-config --libs - with shared objects it makes no difference, but
with static libs this doesn't bring in the needed symbols correctly since
only symbols needed by earlier objects on the command line are brought
in. Reported by Thomas Moschny.
|
|
|
|
| |
somewhat cleaner .so dependencies on ELF systems. Patch from Zack Weinberg.
|
|
|
|
|
|
| |
printfs would complain because it would think that the -L/lib/dir was
an (unknown) option instead of the string. Instead use a plain echo in
each branch of the if, slight code duplication but not a huge deal.
|
|
|
|
|
|
|
| |
because that totally breaks with static libs. OTOH, not using the version
number totally breaks if more than one version is installed.
Kind of a tradeoff...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
both support TR1 fine AFAICT.
Add ability to explicitly disable using TR1 with --with-tr1=none
Add a marker in the cc info files specifiying if TR1 should be chosen
by default. Yes, autoconf would be better for this than a static
per-compiler setting. Yes, I totally hate autoconf. Yes, I would still
consider autoconf patches. No, I'm not going to do it myself. :)
I am looking forward to being able to safely adopt C++0x and TR2
throughout the library and make the need for a lot of this special-casing
stuff go away.
Until then, it seems better to defaulting to using tr1 (and thus, ECC) than
not.
|
| |
|
| |
|
|
|
|
| |
instead of runtime configurable.
|
|
|
|
|
|
|
|
| |
so we link against the specific intended version of the library, for instance
-lbotan-1.7.20 rather than simply -lbotan
This again seems especially an improvement where you want more than one
version installed (1.6 vs 1.7, for instance).
|
| |
|
| |
|
|
|
|
|
|
|
| |
$ pkg-config botan-17 --libs
-L/usr/local/lib -lbotan -lm -lpthread -lrt
to make it easier to have multiple versions of Botan installed and in
use at the same time.
|
|
|
|
| |
detected (as on FreeBSD)
|
| |
|
|
|
|
| |
most Intel Core Duo (32 bit, as opposed to Core 2 Duo being 64 bit).
|