> On Mon, Feb 02, 2004 at 09:10:53AM -0000, gl wrote:
> > 2) The use of the word 'hash' clashes with my installed STLport (version
> > 4.5) in a couple of places - I simply renamed it '_hash' (patches
attached).
>
> Why can't this be fixed in STLport instead?

Hmm, well, it seems to be part of the hash_map container.  The conflict
arises from a definition in STLport's 'hash_fun.h'.  It makes sense to me to
work around this in crypto, considering it's such a small fix (it's just a
parameter name in a couple of calls).

..\cryptlib5.1\iterhash.h(91) : error C2955: 'hash' : use of class template
requires template argument list
        D:\STLPORT\STLPORT\stl/_hash_fun.h(40) : see declaration of 'hash'

> > And finally, the bad news - the new version bloats my app by 20K (I was
> > hoping it would reduce it).  Is there anything I can do with this
version to
> > reduce code size?
>
> I don't know. I wish I had tool for profiling code size, that would take
> an .exe and give a list of demangled names of functions that are linked
> into it and the size of each function. Does anyone know of a tool like
> this?

Funny, I've been wondering about exactly the same thing only a few days ago.
I did a quick search at the time but couldn't find anything.  Surely a tool
like that must exist?

> In the mean time, try removing .cpp files that aren't being used from the
> library. It's very unlikely, but maybe the linker is bring in stuff it
> doesn't need. Also, try VC++ .NET 2003 if you can. Its whole program
> optimization is very good at reducing code size.

I'll try the .cpp approach - unfortunately I don't have access to .Net.
Thanks.
--
gl

Reply via email to