From: Diego Novillo <dnovillo@redhat.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: Mark Mitchell <mark@codesourcery.com>,
Richard Henderson <rth@redhat.com>,
gcc@gcc.gnu.org
Subject: Re: pruning unused debugging types (enums/PR23336)
Date: Wed, 15 Feb 2006 13:48:00 -0000 [thread overview]
Message-ID: <43F330CE.7020700@redhat.com> (raw)
In-Reply-To: <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.
prev parent reply other threads:[~2006-02-15 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 22:08 Aldy Hernandez
2005-11-17 23:09 ` Richard Henderson
2005-11-18 6:24 ` Mark Mitchell
2005-11-18 20:09 ` Aldy Hernandez
2005-11-19 1:03 ` Mark Mitchell
2006-02-10 20:03 ` Aldy Hernandez
2006-02-14 2:11 ` Mark Mitchell
2006-02-14 11:52 ` Aldy Hernandez
2006-02-15 2:08 ` Mark Mitchell
2006-02-16 19:42 ` Aldy Hernandez
2006-02-17 23:53 ` Richard Henderson
2006-02-15 13:48 ` Diego Novillo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43F330CE.7020700@redhat.com \
--to=dnovillo@redhat.com \
--cc=aldyh@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=rth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).