Wei,
The vtable removal did make a small difference. The dll is now 442368
bytes in size. I.e. it shaved off a tad over 8000 bytes.
Do you think I'd save much space if I managed to pare my use of crypto++
down to just using it to decrypt and remove the padding from the signature?
If it's going to take me 10 hours to make it significantly smaller then it's
probably good enough as is. But if I could shave off another 50+k in 3-4
hours it would probably be worth it. I want to be very clear that I am not
complaining here. :) I just want to shed some light on how I'm weighing the
tradeoffs.
Thanks for your assistance and for making crypto++ available,
John Stewart
----- Original Message -----
From: "Wei Dai" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 15, 2003 8:53 PM
Subject: Re: trying to make my crypto++ using executable smaller
> MSVC 6 is not smart enough to figure out on its own when vtables can be
> safely omitted, and a lot of wasted space seem to be taken up by these
> unused vtables. I've added a bunch of __declspec(novtable) to the latest
> code in CVS. Please try it out. It should reduce the size signficantly.
