Tools for Analyzing C++ Class Code Generation?

Milo_Mindbender submits this query: "I've got a midsize Linux project which uses a lot of STL and other C++ template code. Even considering this, I end up with a lot bigger text (generated code) segment than expected. I know the information about the amount of code generated for each class is in the objdump, but prying it out by hand is a problem when you get five line long template invocations and hundreds of methods to wade through. Can anyone can recommend some tools that analyze binary or objdump output and summarize the amount of code generated for each class, including each unique template or STL class?"

Comments

Re:This article should have been called

[be-fan]

Too bad that C++ templates have nothing to do with OOP, but rather procedural programming. And while they have lots of problems (like code bloat) they are also phenomenally powerful for certain things (generic data structures). Even if you write nothing about procedural code, you could benifet from templates.

Me Too!

[kzadot]

Our large corporation also has a project, a client has requested that we implement BubbleSort, QuickSort, ShellSort, and one other sort that we learnt in cl^H^H^H^H^H^H^H^H^H err, discussed in a business meeting. The err, client also requests a 1 page analysis comparing and contrasting the differences between the searches.

Can code generation do this? It could really increase my chances of a good mar^H^H^H err profit yeah.

OpenC++

[angel'o'sphere]

Search at source forge for Open C++ or OpenCPP, not sure how it is written.

That is a programmable source to source transformer for C++.

It spits out one singel file of c++ for every compiled C++ unit, removing the includes, by expanding them into the output.

That way yo can source level debug the processed c++ code, not exactly what you want but likely more powerfull in the long run anyway.

Your request varies far to heavy from compiler to compiler.

angel'o'sphere

Reducing template bloat

[mattgreen]

Enough uninformed comments already. Most STL code bloat can be controlled pretty easily. What you do is make a wrapper over an STL class. For example if you're using std::vector you'd make a Vector class:

template<typename T>
class Vector
{
public:
//ctors as necessary
Vector();

T get(size_t i)
{
return static_cast<T>(vec[i]);
}

void insert(T item)
{
vec.push_back(static_cast<void*>(item));
}

pri vate:
std::vector<void*> vec;
};

You may wish to provide the exact functionality of the container you're wrapping, or you may wish to change the semantics. It's up to you.

It is kinda ugly for what it does but it works. Only one instantiation of std::vector is made, it is void*. Putting the member function definitions in the header file ensures they will be inlined if necessary.

I think Scott Meyers came up with this tip first.

Re:Reducing template bloat

[saurik]

If your data type really can be static_cast'd to a void * then there's probably a much better solution to this problem in almost 90% of the cases: it's called a "better compiler". I don't know what compiler you are using, but Visual Studio .NET finds functions whose assembly code generated the same and merges them (or whatever you want to call it: links all usages to the same implementation) at link time.

So if you have a vector of int * and a vector of long * and a vector of MyObject * and a vector of unsigned long they should all generate the same assembly code and you should only end up with a single set of these in your resulting binary.