Code size "profiling"

[Igor R.]

Hello,

I've got a "code bloat" problem (probably due to multiple templates
instantiations) that I try to handle.
However, trying to determine suspect code at a glance is like trying
to optimize performance without a profiler. So my question is whether
there's any "profiling-like" technique that allows to put the finger
on specific places in the code that produce the bloat?

Thanks!

[Igor R.]

After investingating this topic a bit more, I found the following
opensource tool:
http://aras-p.info/projSizer.html
which uses Microsoft msdia*.dll to extract the information from *.pdb
file.

Analyzing its logs raised another question. Among various code and
data listed in the logs, there's the following line:

Data by size (kilobytes):
1854.51: __NULL_IMPORT_DESCRIPTOR
KERNEL32.dll
........


Does anyone know, what __NULL_IMPORT_DESCRIPTOR is and what might
cause it to take ~2Mb of the executable?

Thanks.