atom feed9 messages in org.freebsd.freebsd-archRe: Getting rid of libgmp
FromSent OnAttachments
Dima DorfmanJul 13, 2001 6:55 am 
Terry LambertJul 13, 2001 11:39 am 
Dima DorfmanJul 14, 2001 1:52 am 
Peter WemmJul 14, 2001 6:06 am 
Dima DorfmanJul 14, 2001 6:23 am 
Steve KarglJul 14, 2001 7:47 am 
Terry LambertJul 16, 2001 8:15 am 
Peter PentchevJul 16, 2001 8:40 am 
Kris KennawayJul 16, 2001 12:29 pm 
Subject:Re: Getting rid of libgmp
From:Dima Dorfman (di@unixfreak.org)
Date:Jul 14, 2001 1:52:54 am
List:org.freebsd.freebsd-arch

Terry Lambert <tlam@mindspring.com> writes:

Dima Dorfman wrote:

Hi folks,

A week or so ago there was a thread on -current about removing libgmp. It was generally agreed that this was a good idea, but (as usual) somebody has to do the work, and some people wanted FreeBSD to continue to supply a libmp-compatible interface.

To satisfy both groups, I propose that we import a libmp that is implemented in terms of the OpenSSL BIGNUM library. Attached below is a sharball of such an implementation. I couldn't find very good documentation on the libmp interface, but I've tested this with most[1] of the software in FreeBSD that uses libmp, and all programs work as well as they did before.

The library is quite small; all functions except msqrt() have a BIGNUM equivilent. It requires that the program using it be linked with -lcrypto[2].

Comments? Suggestions?

Benchmarks, proving that you increased, or at least did not injure performance with this change?

My wrapper around OpenSSL's BIGNUM library doesn't introduce any performance penalties beyond one or two more 'call' instructions. If OpenSSL's BIGNUM library is slower than libgmp (and it probably is), then someone just needs to fix that. The fact that I decided to write a wrapper around BIGNUM instead of converting all the programs which use libmp to use BIGNUM is better from a performance point of view; at least this way it's easier to change to another BIGNUM implementation (you'd only have to change this library instead of all those programs).

Besides, as has been discussed before, all the applications this is used for in FreeBSD are not performance-critical.

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message