This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: pruning unused debugging types (enums/PR23336)
- From: Diego Novillo <dnovillo at redhat dot com>
- To: Aldy Hernandez <aldyh at redhat dot com>
- Cc: Mark Mitchell <mark at codesourcery dot com>, Richard Henderson <rth at redhat dot com>, gcc at gcc dot gnu dot org
- Date: Wed, 15 Feb 2006 08:46:54 -0500
- Subject: Re: pruning unused debugging types (enums/PR23336)
- References: <20051117220835.GA8907@redhat.com> <20051117230925.GB21279@redhat.com> <437D7395.8080000@codesourcery.com> <m3k6c3c78v.fsf@pantani.quesejoda.com> <43F13C3B.7050008@codesourcery.com> <20060214115052.GA29895@redhat.com>
Aldy Hernandez wrote:
>> You could combine the two ideas: a global hash table of types used in
>> casts, where each entry had a list of functions using those types. That
>> should take up no more storage than the per-function vectors. Then,
>> you'd have to walk the entire hash table, writing out each type for
>> which at least one of the associated functions was written out,
>> including being inlined into another function.
>
> Do we keep a hash of functions that have been written out somewhere?
>
You need a list of functions that have been written or scheduled to be
emitted? Each node in the call graph has a field 'output' set to true
when the function is marked for generation.