Libgcrypt and libgmp
Werner Koch
wk at gnupg.org
Mon Sep 8 20:30:44 CEST 2014
On Fri, 5 Sep 2014 00:14, dbaryshkov at gmail.com said:
> dual-licensed under GPLv2+ or LGPLv3+. As far as I understand, this
> licensing is compatible
> with libgcrypt LGPLv2.1+.
Nevertheless I like to stick to LGPLv2.1+.
> Surprisingly even replacing several asm-coded functions resulted in
> nearly 20-25% speed
> increase (according to tests/benchmark pubkey). Do such patches have a
> chance to be
That obviously depends on on the architecture. We have quite new code
for amd64.
Libgcrypt (formerly GnuPG) are based on GMP version 2 which is 20 years
old. Back then there was no public development and the later
improvements with GMP 3 never made it to Libgcrypt because the build
system of GMP was heavily changed and nobody volunteered to convert that
to the Libgcrypt system. Might have also been a linceses issue - I
can't remember.
> reviewed & accepted, or it is a waste of time, as you would prefer to
> keep libgcrypt
> independent of libgmp. I'm not changing the gcry_mpi_t internals, or
Thanks for the offer. However, I do not want to have a dependency on
another library. Further, forthcoming improvements will likely be all
in the ECC area and optimization is curve dependent.
Salam-Shalom,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
More information about the Gcrypt-devel
mailing list