This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: debug symbol size
- To: alex at anvil dot co dot uk (Alex Hornby)
- Subject: Re: debug symbol size
- From: Joern Rennecke <amylaar at redhat dot com>
- Date: Thu, 7 Dec 2000 22:20:57 +0000 (GMT)
- Cc: jbuck at racerx dot synopsys dot com (Joe Buck), gcc at gcc dot gnu dot org
> Note the . of .text. I was trying to say that for such a small text
> segment there was perhaps an excessive amount of debug information
> output.
In a previous discussion, IIRC, the verdict was that the types need
most of the debugging symbol space for small programs.
In a way this is a feature of C++: you #include information for a bootload
of types, and it is hard to tell which of these someone who debugs the
program might be intrested in.
Consider the case where an intermediate variable was optimized away.
The programmer might still want to cast a value to the type of that
variable, even if there is no variable of that type left.
And in C++, with all its virtual superclasses and containers that
might contain all sorts of things, it's also hard to tell which types
could possibly be used by the program.